Skip to content
FeedX

FeedX field guide AI use cases

AI use cases.
Ready to try.

Tell your AI assistant what you want to achieve. Use these practical recipes to turn your products, media, and ideas into work you can review in FeedX.

ChatGPT · Claude · Perplexity · Grok
Use your preferred language. Replace anything in [brackets].

01

Give it the context

Name your workspace, product or exact media, audience, and goal.

02

Shape it in conversation

Ask for options. Choose one. Refine the copy and preview the actual media.

03

Be specific at delivery

Review the account names, date, and timezone. Approve the exact version.

Complete workflows

Create in chat. Deliver with FeedX.

Follow one sequence from your starting idea to a checked delivery result. Copy each message when you reach that step. You can create the asset before mentioning FeedX.

8 complete workflows
01Your idea → an image → a published postCreate the image in chat first, then ask FeedX to use that exact result.Follow a complete workflow

Before you beginAn assistant with image generation, a connected FeedX workspace, and named image-compatible accounts.

  1. Step 1Create and inspect the image

    TRY THIS PROMPT
    Create a square image about [brief] for [audience], with [visual style]. Show the actual image so I can review it. We will prepare the post copy when I hand it to FeedX.
  2. Step 2Mention FeedX and request delivery

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. I approve the exact image above. Write and choose a caption from my brief in [language] with a [tone] voice, then publish now to [exact account names] as an image post. Keep the image unchanged. Complete required channel settings with me, then continue publishing.
  3. Step 3Check the actual result

    TRY THIS PROMPT
    @FeedX, check the campaign you just submitted once. Show the result for each named account and any confirmed post links. Do not publish again.

What can affect this flowA chat image must be transferable as the original file. If it is not, use the FeedX upload link, return and say “Done”; FeedX then resumes the same request. Connection alone does not publish.

Link to this workflow ↗
02A product → a new image → a published postStart with verified product facts, create a visual in your assistant, then deliver it through FeedX.Follow a complete workflow

Before you beginA catalog workspace, a product from that store, image generation in your assistant, and connected accounts.

  1. Step 1Get the real product

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. Find this exact product: [product URL]. Show its current facts and original image links for a post aimed at [audience].
  2. Step 2Create the actual visual in chat

    TRY THIS PROMPT
    Using the verified product facts and the product photo I select, create a [format] image in [visual style]. Preserve the product appearance, packaging, label, and logo. Write a matching caption without invented discounts. Show the finished image and caption for my review.
  3. Step 3Publish the chosen result

    TRY THIS PROMPT
    @FeedX, I approve this exact image and caption for the product we selected. Publish them now to [exact account names]. Keep the image unchanged, recheck the product facts, and continue through any required account settings. If the facts changed, show me before delivery.
  4. Step 4Read the delivery outcome

    TRY THIS PROMPT
    @FeedX, check this campaign once and show which accounts succeeded, remain pending, or need attention, with returned post links.

What can affect this flowAn image URL is not proof the assistant inspected the image. Make the selected reference image accessible and inspect the generated product details before approving. Product lookup stays in the selected store.

Link to this workflow ↗
03Your brief → a finished Reel → deliveryGenerate a playable video from your idea, then hand the finished file to FeedX.Follow a complete workflow

Before you beginActual video creation available in your assistant, or a video you create separately; connected short-video accounts.

  1. Step 1Generate and watch the video

    TRY THIS PROMPT
    Create a vertical 9:16 video about [brief] for [audience], around [duration] seconds long, with [scene direction]. Write a matching caption in [language]. Show a playable final video and the caption. If video creation is unavailable, tell me; do not present a storyboard as a finished Reel.
  2. Step 2Publish the exact video

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. I have watched and approve the exact video and caption above. Publish them now as a Reel to [exact account names]. Preserve the original video and audio. Complete required account settings with me and continue to delivery.
  3. Step 3Check each destination

    TRY THIS PROMPT
    @FeedX, check the submitted video campaign once. List confirmed successes, pending accounts, failures, and any returned live links. Do not submit another post.

What can affect this flowVideo creation is not available in every assistant or plan. An existing playable file can be uploaded instead. Imported original audio stays unchanged unless you request a different soundtrack.

Link to this workflow ↗
04Product photos → a Reel → a scheduled postTurn selected product photos into an actual video and choose a precise delivery time.Follow a complete workflow

Before you beginA catalog product, accessible source photos, video creation in your assistant, and compatible accounts.

  1. Step 1Choose the source product

    TRY THIS PROMPT
    @FeedX, in [workspace] for [brand], find [product URL]. Show the verified product facts and original photos. I want a short product video for [audience].
  2. Step 2Make and review the finished Reel

    TRY THIS PROMPT
    Using the product photos I select and its verified details, create a vertical [duration]-second video with [scene sequence]. Keep the product recognizable. Write a caption in [language] and show the playable video. Tell me if actual video creation is unavailable.
  3. Step 3Schedule the approved result

    TRY THIS PROMPT
    @FeedX, I approve this exact video and caption. Schedule them as a Reel to [exact account names] on [YYYY-MM-DD] at [time] in [timezone]. Preserve the video and original audio. Complete required account settings with me, then submit the schedule.
  4. Step 4Verify the saved schedule

    TRY THIS PROMPT
    @FeedX, show the accepted campaign links and check the calendar for that exact date in [timezone]. Confirm the named accounts and scheduled time; do not create another schedule.

What can affect this flowScheduled does not mean published. If the final video is unavailable in chat, upload a finished original file or explicitly choose a FeedX render after reviewing its cost.

Link to this workflow ↗
05A file you already made → every eligible accountBring finished creative from another tool or earlier in your chat and ask FeedX to deliver it.Follow a complete workflow

Before you beginThe original image or playable video, approved copy or permission to write it, and connected accounts.

  1. Step 1Make the finished asset available

    TRY THIS PROMPT
    Here is the original [image or video] I created in [tool]. Use this exact file and this approved caption: [caption]. Do not regenerate or edit the asset.
  2. Step 2Request the complete delivery

    TRY THIS PROMPT
    @FeedX, in [workspace] for [brand], publish the exact file and approved caption above now as [image post or Reel] to every compatible connected account. Explain any incompatible accounts, keep all eligible accounts, and complete required channel settings with me before continuing.
  3. Step 3Finish a file handoff if needed

    If FeedX asks you to upload the original file, use the upload step. Otherwise, continue to the result check.

    TRY THIS PROMPT
    Done—I uploaded the original file through the FeedX link you provided. Continue the same publishing request using that exact file, approved caption, and destination set.
  4. Step 4Check the full account set

    TRY THIS PROMPT
    @FeedX, check all campaigns returned for this request once. Show each destination exactly once with its current result and any confirmed links.

What can affect this flowThe upload step is only needed when direct handoff cannot access the file. An image is ineligible for YouTube. Larger account sets may be split; a later eligible batch must not be silently skipped.

Link to this workflow ↗
06A vertical video → a native StoryCreate all visible words inside the video, then publish as a Story rather than a Reel.Follow a complete workflow

Before you beginA finished vertical video and eligible Facebook or Instagram Story accounts.

  1. Step 1Create the complete Story video

    TRY THIS PROMPT
    Create a vertical 9:16 video for [brief], with all intended words and visuals already inside the video. Show a playable final file so I can review it. Tell me if actual video creation is unavailable.
  2. Step 2Mention FeedX and choose Story placement

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. I approve the exact video above. Publish it now as a native Story to [exact Facebook or Instagram account names]. Check Story support; do not convert it to a Reel or add a separate caption.
  3. Step 3Check Story delivery

    TRY THIS PROMPT
    @FeedX, check that Story campaign once. Show the current result for each account without posting the video again.

What can affect this flowCurrent FeedX Stories use video on supported Facebook and Instagram accounts. All seller-visible words must already be in the video; there is no separate caption, CTA, hashtag set, or alt text.

Link to this workflow ↗
07Seven finished assets → an approved publishing weekCreate a small series, then review and schedule the complete week through FeedX.Follow a complete workflow

Before you beginUp to seven distinct approved assets, reviewed copy, connected accounts, and a date range.

  1. Step 1Create and review the series

    TRY THIS PROMPT
    Create [one to seven] distinct [images or playable videos] around [theme]. Give each day its own asset and caption in [language]. Show each actual result for review; keep a clear day-to-file mapping. Tell me if the requested generation is unavailable.
  2. Step 2Ask FeedX to prepare the whole plan

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. I approve these assets and captions. Prepare one post per day from [start date] at [time] in [timezone] for [exact account names]. Keep each day’s exact file. Complete settings for the whole series and show the entire plan before scheduling.
  3. Step 3Approve the reviewed week

    TRY THIS PROMPT
    I approve this unchanged week with the shown posts, files, named accounts, dates, and times in [timezone]. @FeedX, schedule the full plan now.
  4. Step 4Check accepted and remaining items

    TRY THIS PROMPT
    @FeedX, show which items were accepted, remain drafts, or failed, with the returned campaign links. Check the calendar once and preserve all accepted work.

What can affect this flowA publishing week has one to seven content items within seven local days. Each day can span multiple account batches, but must keep its own media. A plan limit may leave some items unfinished.

Link to this workflow ↗
08Product photos → a saved video template → a reviewed ReelChoose an enabled FeedX campaign video template, approve one render, watch the finished video, then authorize delivery.Follow a complete workflow

Before you beginA selected catalog product with usable original photos, an enabled video template, eligible Reel accounts, and sufficient approved render allowance.

  1. Step 1Find the product and available templates

    TRY THIS PROMPT
    @FeedX, use [workspace] and [brand]. Resolve [product URL] and check Reel support for [exact account names]. Show the product's original photo links and the enabled campaign video templates, including their current required inputs, photo limits, duration, and output format. Let me choose a template; do not render or publish.
  2. Step 2Review the exact inputs and one-render cost

    TRY THIS PROMPT
    @FeedX, prepare [chosen template] using [exact original photo references]. Propose the template's required on-screen text and a Reel caption in [language] using verified product facts. Show the current template version, selected photos, text, duration, framing, audio choice, exact accounts, and allowance or quoted cost for one render. Do not start rendering.
  3. Step 3Approve one render and watch the result

    TRY THIS PROMPT
    I approve one render with the unchanged template version, photos, text, framing, audio choice, and displayed allowance or quoted cost. @FeedX, start that render once and return its status. When it completes, show the actual playable video for review. Do not create extra versions or publish.
  4. Step 4Approve the finished Reel for delivery

    TRY THIS PROMPT
    @FeedX, I have watched and approve this exact finished video and caption. Publish the unchanged result now as a Reel to [exact account names]. Complete any required account settings with me, then continue the same delivery. Return the accepted campaign references without claiming publication before a confirmed destination result.
  5. Step 5Check each destination once

    TRY THIS PROMPT
    @FeedX, check those accepted campaign references once. Show each named account's current delivery outcome and any confirmed post link. Keep pending, failed, and uncertain results clear; do not retry or create another campaign.

What can affect this flowThe chosen enabled template controls the required photos, text, and duration. Approval covers one render at the reviewed allowance or cost. Queued rendering is not a playable video, and render approval does not authorize publishing.

Link to this workflow ↗

The prompt library

What would you like to do?

39 recipes

Connect FeedX and choose your workspace

Start with the right account, workspace, brand, and connected destinations before creating content.

Any workspaceStart here Connect FeedX to your assistant A connection guide that matches the assistant you actually use. See the prompt

Bring thisA FeedX account and an assistant that supports the FeedX app or a custom MCP connection.

TRY THIS PROMPT
Help me connect FeedX to [ChatGPT, Claude, or Perplexity]. Use the connection method available in this assistant. Explain the sign-in and access approval steps, then check which FeedX account is connected.

Good to knowAn assistant's connector availability depends on its plan and settings. Connecting FeedX does not create or publish a post.

Link to this use case
Any workspaceStart here Choose the correct workspace The actual workspace is identified before any content or catalog action. See the prompt

Bring thisA connected FeedX account with access to a workspace.

TRY THIS PROMPT
@FeedX, show my connected account and accessible workspaces. Identify [workspace name or store domain] and its capabilities. Do not create a new workspace or change settings.

Good to knowA standalone workspace supports media-first posts. Catalog actions require an eligible connected store.

Link to this use case
Any workspaceStart here Use an existing brand's voice Content uses the chosen workspace and a real brand profile. See the prompt

Bring thisA workspace containing the brand you want to use.

TRY THIS PROMPT
@FeedX, use [workspace]. Show its existing brands and the voice settings for [brand name]. Use that brand for the next draft; do not create or edit a brand.

Good to knowBrand selection sets the context. It does not select social accounts or authorize publishing.

Link to this use case
Any workspaceStart here Check accounts before making a post A clear list of connected accounts, formats, and missing delivery settings. See the prompt

Bring thisA connected FeedX workspace.

TRY THIS PROMPT
@FeedX, in [workspace], list my connected social accounts and check which support [text post, image post, Reel, or Story]. Show any settings I must complete. Do not publish anything.

Good to knowMCP delivery currently covers Facebook, Instagram, Threads, TikTok, Pinterest, YouTube, LinkedIn, X, and Bluesky in their supported formats. Snapchat and Google Business are not MCP publishing destinations.

Link to this use case

Find real products and source material

Read the selected store's catalog, verify product facts, and choose original photos before writing or drawing.

Catalog requiredStart here Find a product in the current store Real catalog results rather than an invented product or an unrelated store link. See the prompt

Bring thisA workspace with an available product catalog.

TRY THIS PROMPT
@FeedX, use [workspace]. Search this store's catalog for [product name or theme]. Show a small selection with names, current product links, and images. Let me choose one before making content.

Good to knowCatalog support depends on the workspace connection and permissions. A standalone workspace has no store catalog.

Link to this use case
Catalog requiredStart here Read one exact product The selected product is resolved inside the correct store. See the prompt

Bring thisA product URL or product identifier from the selected workspace's catalog.

TRY THIS PROMPT
@FeedX, in [workspace], find this exact product: [product URL or ID]. Show its current title, description, available price information, and original image links. Do not switch products.

Good to knowA URL from another store is not a substitute for a product in the current catalog. Do not invent availability, discounts, or specifications.

Link to this use case
Catalog requiredEveryday Choose a product from a collection A focused selection from a real store collection. See the prompt

Bring thisA catalog workspace with collection browsing available.

TRY THIS PROMPT
@FeedX, show the available collections in [workspace]. Find [collection name], then list a few products from it for [audience]. Explain the fit using the returned product facts; wait for my selection.

Good to knowIf this store connection does not expose collections, ask for a catalog search instead. Do not invent collection membership.

Link to this use case
Catalog requiredEveryday Check a photo and promotional claims The creative uses the selected original image and claims supported by the product record. See the prompt

Bring thisA selected product and its accessible original images.

TRY THIS PROMPT
@FeedX, refresh the facts for the selected product. Show its original photo choices and verify these proposed claims: [claims]. Mark anything the catalog does not confirm. Do not create or publish content yet.

Good to knowA returned image link is not proof the assistant inspected the pixels. Make the selected reference accessible before asking for an accurate product visual.

Link to this use case

Create in chat and keep the approved file

Use the assistant's available creative tools, then import the exact approved result into FeedX.

Catalog requiredStart here Draw a product promotion in your assistant An actual promotional image grounded in the chosen product photo and facts. See the prompt

Bring thisA selected catalog product, an accessible source photo, and image generation available in your assistant.

TRY THIS PROMPT
Using the selected product photo and verified facts above, create a square promotional image for [audience] in [visual style]. Preserve the product, label, logo, and packaging. Use only this approved offer: [offer or no offer]. Show the finished image for review.

Good to knowThe assistant creates the image using its own available capability and quota. FeedX MCP does not silently replace unavailable generation with a paid image service.

Link to this use case
Your mediaEveryday Refine a visual before importing it A reviewed final image with only the requested changes. See the prompt

Bring thisAn image accessible in the conversation and image editing available in your assistant.

TRY THIS PROMPT
Edit the image above: [specific change]. Keep the product appearance, logo, and all other approved details unchanged. Show the updated image so I can choose the final version.

Good to knowCheck product details and text in the actual result. Importing an earlier version does not automatically update it after an edit in chat.

Link to this use case
Your mediaStart here Bring the exact approved file into FeedX A saved media asset that corresponds to the file you approved. See the prompt

Bring thisAn accessible original image or playable video and a selected FeedX workspace.

TRY THIS PROMPT
@FeedX, use [workspace]. Import the exact approved [image or video] above without regeneration or edits. Confirm the saved media asset. Do not create a post or publish yet.

Good to knowDirect handoff requires access to the original file. If the assistant cannot transfer it, FeedX can provide an upload link. A preview page or thumbnail is not the original video.

Link to this use case
Any workspaceStart here Write a post without a catalog product A draft based on your brief and brand voice without a fake product attachment. See the prompt

Bring thisA selected workspace, a brief, and exact destination accounts.

TRY THIS PROMPT
@FeedX, in [workspace] for [brand], prepare a post about [brief] for [audience] in [language]. Use these exact accounts: [account names]. This is a productless post. Show the proposed copy and any required media; do not publish.

Good to knowStandalone workspaces support this media-first flow. The assistant writes the proposed content; FeedX saves and delivers the reviewed result.

Link to this use case
Your mediaEveryday Reuse a saved media asset The next draft uses an existing asset rather than an unnecessary new render. See the prompt

Bring thisApproved media already saved in the current FeedX workspace.

TRY THIS PROMPT
@FeedX, in [workspace], find my saved media for [name or description]. Show the matching assets and their available previews. Let me choose the exact file for a new draft; do not regenerate or publish it.

Good to knowUse media you own or are allowed to publish. A video preview should be playable before you approve delivery.

Link to this use case

Make product videos with available templates

Discover enabled FeedX video templates, review their inputs and allowance, and inspect the actual rendered video.

Catalog requiredStart here Choose an available video template A real enabled template suitable for the selected product and format. See the prompt

Bring thisAn eligible catalog product and FeedX video rendering available to the workspace.

TRY THIS PROMPT
@FeedX, show the enabled campaign video templates available for the selected product. Explain each template's required photos, text, duration, and supported output. Let me choose one; do not render yet.

Good to knowTemplates and availability come from the current FeedX configuration. Do not invent a template or describe arbitrary scene cutting as a supported template flow.

Link to this use case
Catalog requiredEveryday Review the product photos and video text A previewable template plan using selected original images and accurate text. See the prompt

Bring thisA selected enabled template and a resolved product with usable photos.

TRY THIS PROMPT
@FeedX, prepare the chosen template with these product photos: [selected photo references]. Propose its required on-screen text and a matching caption in [language] using verified facts. Show the inputs and the allowance or cost for one render. Do not start rendering.

Good to knowOn-screen text must fit the chosen template. Planning or quoting does not create a playable video or authorize a paid render.

Link to this use case
Catalog requiredEveryday Render and review one product video A completed, playable video from the approved enabled template. See the prompt

Bring thisApproved template inputs and explicit approval of the displayed allowance or cost.

TRY THIS PROMPT
@FeedX, I approve one render using the unchanged template, product photos, text, and allowance or cost shown above. Start that render and show its status. When complete, return the playable video for review. Do not publish it.

Good to knowQueued or rendering is not completed. The approval covers one render; it does not authorize extra versions or publishing.

Link to this use case
Your mediaEveryday Choose music without losing the original video An audio choice is checked before changing the approved video. See the prompt

Bring thisA saved video and either its original audio, a named supported track, or an approved saved soundtrack.

TRY THIS PROMPT
@FeedX, in [workspace], I want [keep original audio or use this named track or saved soundtrack] for [video reference]. Check the requested source and show the actual matching track or asset. Explain any processing required before changing it; do not publish.

Good to knowImported video audio stays unchanged unless you ask for a replacement. An audio selection is not proof that the final rendered file contains that sound.

Link to this use case
Catalog requiredEveryday Give your product video a matching color palette Review product-inspired template colors alongside your video copy in New Campaign. See the prompt

Bring thisOriginal product photos, an enabled video template and the applicable AI allowance.

TRY THIS PROMPT
Write a brief for FeedX New Campaign: create a [language] product video for [product]. Base its colors on these actual photos and our supplied brand guidance. Keep the photos unchanged and the text readable. I will review the generated palette in FeedX before rendering.

Good to knowGenerate and review the palette in the FeedX dashboard. AI content generation and rendering are separate actions; photo-inspired colors should not be presented as official brand colors without supplied guidance.

Link to this use case
Catalog requiredEveryday Keep your full copy when preparing a product video Preserve approved captions and first comments while reviewing on-screen text against the template limits. See the prompt

Bring thisOriginal product photos, a compatible video template and destinations that support your requested first comment.

TRY THIS PROMPT
@FeedX, prepare a product Reel for [product]. Keep this approved caption exactly: [caption]. Keep this first comment exactly: [comment]. Propose separate on-screen text within the selected template limits and preserve approved line breaks. Tell me if anything cannot fit. Do not render or publish yet.

Good to knowAutomatic font fitting applies to eligible video text fields; other fields retain their own limits. A long caption does not need to become a long on-screen headline.

Link to this use case

Set up the right delivery for each account

Choose supported formats and complete provider-specific settings without silently adding destinations or changing defaults.

Any workspaceStart here Match a format to the named accounts Only the exact requested accounts are considered, with any incompatible formats explained. See the prompt

Bring thisConnected accounts and a proposed text, image, video, or Story format.

TRY THIS PROMPT
@FeedX, check [format] for these exact accounts in [workspace]: [account names]. Show which are eligible and explain any excluded accounts. Do not replace the format, add accounts, or publish.

Good to knowYouTube requires video. Text-only delivery is limited to supported text destinations. Native Stories use video on eligible Facebook and Instagram accounts.

Link to this use case
Any workspaceEveryday Select the correct Pinterest board The Pin uses a real board belonging to the selected Pinterest account. See the prompt

Bring thisA connected Pinterest account and an image or video draft.

TRY THIS PROMPT
@FeedX, list boards by name for [Pinterest account]. Suggest a board for this reviewed post. Use the board I choose by its exact name for this campaign only; leave saved defaults unchanged.

Good to knowCampaign-specific board selection and persistent Pinterest defaults are different actions. Saved defaults change only when you explicitly request that.

Link to this use case
Your mediaEveryday Complete TikTok's delivery settings The selected TikTok account has confirmed settings before the draft proceeds. See the prompt

Bring thisA connected TikTok account and a supported image or video draft.

TRY THIS PROMPT
@FeedX, check the delivery settings for [TikTok account] and this draft. Show the confirmation page for privacy, interactions, and any required declarations. After I confirm, continue the same draft; do not create a second one.

Good to knowTikTok settings are not arbitrary chat fields. Required confirmation may need the FeedX form, and saved compatibility must still be current for the delivery.

Link to this use case
Your mediaEveryday Prepare a native video Story A draft uses Story placement on eligible Facebook or Instagram accounts. See the prompt

Bring thisA finished vertical video with all visible words already inside it and Story-capable accounts.

TRY THIS PROMPT
@FeedX, use the exact approved vertical video as a native Story for [Facebook or Instagram account names]. Check Story support and prepare a draft. Do not convert it to a Reel, add a separate caption, or publish yet.

Good to knowCurrent MCP Stories are video-only. There is no separate Story caption, CTA, hashtag set, or alt text. A provider may not return a public Story link.

Link to this use case
Any workspaceAdvanced Review a supported Meta collaboration Collaboration choices are checked against the selected Facebook or Instagram destination. See the prompt

Bring thisAn eligible Meta account, a compatible draft, and the intended collaborator details.

TRY THIS PROMPT
@FeedX, check the collaboration options supported for [account name] and this draft. Validate [collaborator details] and show any required settings or confirmation before applying them. Do not publish or assume the collaborator accepted.

Good to knowSupport differs by account, placement, and provider. A sent invitation is not collaborator acceptance, and a published post does not prove the invitation was accepted.

Link to this use case

Review, publish, and schedule your content

Keep drafts, explicit publishing approval, saved schedules, and confirmed delivery as distinct steps.

Any workspaceStart here Inspect the final draft before publishing One reviewed draft with its exact file, copy, destinations, and placement. See the prompt

Bring thisApproved content and any media required by the selected format.

TRY THIS PROMPT
@FeedX, prepare and show the final draft using [approved copy] and [exact approved media] for [account names] as [placement]. Show the caption, links, media, and delivery settings. Do not publish or schedule.

Good to knowThe assistant composes the copy and FeedX stores the reviewed content. A preview or saved draft is not a live post.

Link to this use case
Any workspaceEveryday Publish an approved post now The exact approved draft is submitted to the named accounts with campaign references. See the prompt

Bring thisA final reviewed draft and completed delivery settings.

TRY THIS PROMPT
@FeedX, I approve this unchanged draft, its exact media, copy, placement, and named accounts. Publish it now. Return the accepted campaign references and any account-specific issues; do not claim it is live before checking delivery.

Good to knowAccepted or queued means the request entered delivery. Only a confirmed destination result supports a published claim.

Link to this use case
Any workspaceEveryday Schedule a post with an exact timezone A saved schedule with an unambiguous date, time, and destination set. See the prompt

Bring thisA reviewed draft, completed settings, and a future delivery time.

TRY THIS PROMPT
@FeedX, I approve this exact draft for [account names]. Schedule it on [YYYY-MM-DD] at [HH:MM] in [IANA timezone, such as Asia/Ho_Chi_Minh]. Confirm the accepted campaign and calendar entry. Do not publish now.

Good to knowScheduled does not mean published. Use a full date and timezone instead of an ambiguous phrase such as tomorrow morning.

Link to this use case
Any workspaceAdvanced Review a complete publishing week A one-to-seven-item plan with a clear mapping from each day to its content and media. See the prompt

Bring thisApproved assets or selected catalog products, account names, dates, and a timezone.

TRY THIS PROMPT
@FeedX, prepare [one to seven] distinct posts over seven local days starting [date] for [account names] at [time] in [timezone]. Use [selected products or approved media]. Show every item's exact copy, file, destination, and time before scheduling anything.

Good to knowReviewing a week does not submit it. Account batching or plan limits can cause partial completion; preserve accepted work and report unfinished items.

Link to this use case
Any workspaceEveryday Find posting times from your account history See dated posting suggestions based on your Facebook and Instagram history, with the publishing timezone clearly shown. See the prompt

Bring thisA connected Facebook Page or Instagram professional account, recent posts and your publishing timezone.

TRY THIS PROMPT
@FeedX, use [workspace] and [brand]. Show history-based posting suggestions for [exact account names] in [timezone], starting [date]. Do not change any campaign or publish.

Good to knowThe campaign picker shows up to five suggestions for one account, or up to two per account when several are selected. Limited history may yield fewer results. Past performance does not guarantee future engagement.

Link to this use case
Any workspaceEveryday Let FeedX choose a posting time for your campaign Save a history-based time in your content plan while keeping every selected destination. See the prompt

Bring thisA confirmed workspace and brand, exact destination accounts, an approved post and usable history for the reference account.

TRY THIS PROMPT
@FeedX, keep [Facebook Page] and [Instagram account] as destinations for this approved post. Choose the top suggested time from [reference account] on or after [date] in [timezone] and save it in the content plan. Keep the complete destination list. Do not schedule or publish yet.

Good to knowThe reference account supplies timing evidence; one campaign uses the same chosen time for all its destinations. Choosing a time does not approve publication. If no returned suggestion fits your date constraints, FeedX should explain that instead of inventing a time.

Link to this use case

Improve supported store content

Prepare reviewable product-copy and blog proposals, then deliver only to platforms and permissions that support the action.

Any workspaceEveryday Propose a better product description A reviewable product-copy proposal grounded in the current description and facts. See the prompt

Bring thisA Shopify workspace, or a verified WooCommerce connection exposing product-description rewrite support.

TRY THIS PROMPT
@FeedX, read the current description of [product] in [workspace]. Propose a rewrite for [audience] in [language]. Preserve factual specifications, existing images, and meaningful layout. Show the proposed changes; do not apply them.

Good to knowProduct-description rewriting is not supported for every catalog platform. A saved proposal has not changed the live product.

Link to this use case
Any workspaceAdvanced Review several product-copy proposals Separate proposals for selected products without changing unrelated items. See the prompt

Bring thisA workspace with product-description rewrite support and exact product selections.

TRY THIS PROMPT
@FeedX, prepare description rewrite proposals for these exact products: [product IDs or URLs]. Use [language and tone], preserve verified facts and existing images, and show each proposal separately. Do not apply changes or expand the product set.

Good to knowA batch may be partial. Check proposal status and the current source before resuming; do not repeat already applied changes.

Link to this use case
Any workspaceEveryday Prepare an article for a connected blog A reviewable blog proposal or explicitly requested platform draft. See the prompt

Bring thisA workspace with supported Shopify, Wix, or WordPress blog access and the required permissions.

TRY THIS PROMPT
@FeedX, check blog access in [workspace] and show the available destinations. Prepare an article about [topic] in [language] using [verified references or product facts]. Show its title, body, and proposed featured image. Do not publish it.

Good to knowBlog actions require actual platform support and permissions. SHOPLINE, Datafeed, and standalone workspaces do not gain blog publishing from catalog access.

Link to this use case
Any workspaceAdvanced Deliver a reviewed article revision The exact approved article revision is sent to the named supported blog destination. See the prompt

Bring thisA reviewed current proposal, a supported destination, and permission to write or publish.

TRY THIS PROMPT
@FeedX, I approve the current unchanged revision of [article proposal]. Deliver it to [exact blog destination] as [draft or published]. Preserve the approved body and featured image. Show the delivery reference and check its actual result.

Good to knowDraft and published are different choices. An accepted asynchronous delivery is not proof that the article is live; an edited proposal needs new approval.

Link to this use case

Check results and keep control

Inspect real delivery outcomes, manage eligible future work, and delegate only within explicit limits.

Any workspaceStart here Check whether each account received the post Confirmed, pending, failed, and uncertain outcomes are reported separately. See the prompt

Bring thisCampaign references from an accepted publish or schedule request.

TRY THIS PROMPT
@FeedX, check [campaign references] once. Show each destination's current status, confirmed post link if available, and any actionable failure. Do not publish, retry, or create another campaign.

Good to knowCampaign success, provider acceptance, and a public link are separate evidence. Pending or uncertain results must not be relabeled as published.

Link to this use case
Any workspaceEveryday Inspect and cancel an eligible future post The selected future campaign is checked before any cancellation. See the prompt

Bring thisA campaign scheduled in the future that has not begun processing.

TRY THIS PROMPT
@FeedX, show the calendar for [date range] in [timezone]. Inspect [campaign reference] and tell me whether it is an unprocessed one-time campaign that can be canceled. Do not change it yet.

Good to knowThis is not a general campaign edit, deletion, or blanket pause feature. Started, completed, and recurring work may not support this cancellation action.

Link to this use case
Any workspaceAdvanced Investigate a failure before retrying A retry decision based on the specific destination and saved provider outcome. See the prompt

Bring thisA campaign or post showing failed, unstarted, or uncertain delivery.

TRY THIS PROMPT
@FeedX, inspect the failure for [campaign and account]. Check whether the provider already accepted or published it, explain the error, and show the eligible retry or failed-post republish action. Do not retry yet.

Good to knowAn uncertain provider result is not a safe reason to republish. Retry support is limited to eligible campaign states and failed posts.

Link to this use case
Any workspaceAdvanced Delegate within explicit limits A reviewable autonomy plan with a workspace, scope, accounts, limits, and expiry. See the prompt

Bring thisAn accessible workspace with the required capabilities and a defined delegation goal.

TRY THIS PROMPT
@FeedX, propose a bounded plan to [draft, schedule, or publish] in [workspace] for [exact accounts]. Limit it to [content scope], [maximum items], [maximum credits], [date range], and [expiry]. Show the settings and remaining allowance. Do not enable it until I approve.

Good to knowDrafting, scheduling, and publishing are separate modes. Delegation must not expand its scope, destinations, budget, or expiry, and does not bypass provider requirements. A saved policy does not start a continuously running background agent.

Link to this use case

Make it your own

A useful brief has six ingredients.

You do not need to know tool names. Give the assistant enough context to make a useful first draft.

  1. Workspace & brand
  2. Product or exact media
  3. Audience & goal
  4. Format & account names
  5. Voice & language
  6. Review, budget & timing
YOUR REUSABLE BRIEF
Use FeedX in [workspace] for [brand]. Start from [product URL or exact approved media]. Help [audience] understand [benefit or goal]. Prepare [format] for [connected account names] in [language], with a [tone] voice. Use verified product facts. Show the draft and exact media first. Tell me any credit cost before paid generation. Propose [date and time] in [timezone], and wait for me to approve delivery.

Refine one thing at a time: “Keep the image. Shorten the caption. Make the call to action softer.”

From idea to confirmed result

A few things make all the difference.

Choose the right starting point

Catalog workspaces can use their current products. Standalone workspaces can start from your media and brief. Shopify product descriptions and blog publishing require an eligible Shopify workspace.

Keep the exact media

An image in your chat is not automatically accessible to FeedX. If the assistant offers a FeedX upload link, use it to hand over the original file. Otherwise, upload it in FeedX and finish the draft there. A similar image is not the same asset.

Name the destination and format

“Instagram” can mean an image post, a Reel, or a Story. Ask which formats your actual connected account supports. Video Stories, Pinterest boards, TikTok settings, and other channel requirements need their own review.

Review what will actually go out

Read the final caption, inspect the image or play the video, and check each named account. If the content, media, destinations, or time change, review the new version before approving it.

Know which limits apply

FeedX MCP access is included with Free, Lite, Pro, and Business. AI credits, renders, store-content updates, and publishing allowances still depend on your workspace. Your AI platform has its own subscription and limits.

Check the result before retrying

Draft saved, scheduled, queued, and published are different states. Queued means delivery is processing. Ask for the result for each account, and check an uncertain request before repeating it.