Give it the context
Name your workspace, product or exact media, audience, and goal.
FeedX field guide AI use cases
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.
Name your workspace, product or exact media, audience, and goal.
Ask for options. Choose one. Refine the copy and preview the actual media.
Review the account names, date, and timezone. Approve the exact version.
Complete workflows
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.
Before you beginAn assistant with image generation, a connected FeedX workspace, and named image-compatible accounts.
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.
@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.
@FeedX, check the campaign you just submitted once. Show the result for each named account and any confirmed post links. Do not publish again.
FeedX writes the delegated copy, accepts delivery, and returns campaign links. A later status check distinguishes successful, pending, and failed accounts.
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 ↗Before you beginA catalog workspace, a product from that store, image generation in your assistant, and connected accounts.
@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].
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.
@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.
@FeedX, check this campaign once and show which accounts succeeded, remain pending, or need attention, with returned post links.
The delivered post uses the selected product, the exact approved image, and the reviewed copy.
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 ↗Before you beginActual video creation available in your assistant, or a video you create separately; connected short-video accounts.
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.
@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.
@FeedX, check the submitted video campaign once. List confirmed successes, pending accounts, failures, and any returned live links. Do not submit another post.
A ready video is imported and submitted to the compatible accounts. The result is confirmed per destination.
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 ↗Before you beginA catalog product, accessible source photos, video creation in your assistant, and compatible accounts.
@FeedX, in [workspace] for [brand], find [product URL]. Show the verified product facts and original photos. I want a short product video for [audience].
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.
@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.
@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.
An accepted schedule is visible in FeedX with its exact date, timezone, and destinations.
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 ↗Before you beginThe original image or playable video, approved copy or permission to write it, and connected accounts.
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.
@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.
If FeedX asks you to upload the original file, use the upload step. Otherwise, continue to the result check.
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.
@FeedX, check all campaigns returned for this request once. Show each destination exactly once with its current result and any confirmed links.
Every eligible account is included, even when FeedX splits the request into multiple campaigns.
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 ↗Before you beginA finished vertical video and eligible Facebook or Instagram Story accounts.
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.
@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.
@FeedX, check that Story campaign once. Show the current result for each account without posting the video again.
The approved video is submitted with native Story placement to eligible named accounts.
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 ↗Before you beginUp to seven distinct approved assets, reviewed copy, connected accounts, and a date range.
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.
@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.
I approve this unchanged week with the shown posts, files, named accounts, dates, and times in [timezone]. @FeedX, schedule the full plan now.
@FeedX, show which items were accepted, remain drafts, or failed, with the returned campaign links. Check the calendar once and preserve all accepted work.
The complete reviewed plan is submitted; FeedX reports any partially completed items instead of claiming the whole week succeeded.
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 ↗Before you beginA selected catalog product with usable original photos, an enabled video template, eligible Reel accounts, and sufficient approved render allowance.
@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.
@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.
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.
@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.
@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.
The approved playable video is submitted to the exact Reel accounts, with a separate confirmed or pending result for each destination.
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
Try a broader term such as “image”, “schedule”, or “Shopify”, or clear the filters.
Start with the right account, workspace, brand, and connected destinations before creating content.
Bring thisA FeedX account and an assistant that supports the FeedX app or a custom MCP connection.
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.
After connecting, choose your workspace before asking for catalog or publishing work.
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 caseBring thisA connected FeedX account with access to a workspace.
@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.
Ask FeedX to use the exact workspace returned by the lookup.
Good to knowA standalone workspace supports media-first posts. Catalog actions require an eligible connected store.
Link to this use caseBring thisA workspace containing the brand you want to use.
@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.
Give the assistant an audience, message, and language for one post.
Good to knowBrand selection sets the context. It does not select social accounts or authorize publishing.
Link to this use caseBring thisA connected FeedX workspace.
@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.
Choose exact eligible account names for the draft.
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 caseRead the selected store's catalog, verify product facts, and choose original photos before writing or drawing.
Bring thisA workspace with an available product catalog.
@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.
Select one returned product and ask for its current details.
Good to knowCatalog support depends on the workspace connection and permissions. A standalone workspace has no store catalog.
Link to this use caseBring thisA product URL or product identifier from the selected workspace's catalog.
@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.
Choose the facts and source photo to use in your draft.
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 caseBring thisA catalog workspace with collection browsing available.
@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.
Choose one product and one original photo for the post.
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 caseBring thisA selected product and its accessible original images.
@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.
Approve one source image and remove unsupported claims from the brief.
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 caseBring thisAn eligible catalog workspace and a resolved product.
@FeedX, create a short link for the exact product we selected in [workspace]. Show the final short URL and its destination. Do not create a campaign or publish a post.
Use the verified link in approved copy where the selected channel supports it.
Good to knowShort links require catalog support. A short link is not a published social post and does not guarantee that a channel will display a clickable link.
Link to this use caseUse the assistant's available creative tools, then import the exact approved result into FeedX.
Bring thisA selected catalog product, an accessible source photo, and image generation available in your assistant.
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.
Approve the result, then ask FeedX to import that exact image.
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 caseBring thisAn image accessible in the conversation and image editing available in your assistant.
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.
Tell FeedX which exact version is approved for import.
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 caseBring thisAn accessible original image or playable video and a selected FeedX workspace.
@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.
Use the saved asset with reviewed copy to prepare a draft.
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 caseBring thisA selected workspace, a brief, and exact destination accounts.
@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.
Approve the copy and supply an exact image or video if the format needs one.
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 caseBring thisApproved media already saved in the current FeedX workspace.
@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.
Select the asset and ask for copy tailored to the named accounts.
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 caseDiscover enabled FeedX video templates, review their inputs and allowance, and inspect the actual rendered video.
Bring thisAn eligible catalog product and FeedX video rendering available to the workspace.
@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.
Select a returned template and prepare its required inputs.
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 caseBring thisA selected enabled template and a resolved product with usable photos.
@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.
Approve the exact inputs and one render after reviewing the allowance or quoted cost.
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 caseBring thisApproved template inputs and explicit approval of the displayed allowance or cost.
@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.
Watch the result, check its text and sound, then approve the exact finished video for delivery.
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 caseBring thisA saved video and either its original audio, a named supported track, or an approved saved soundtrack.
@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.
Approve the specific audio action, then listen to the final playable video.
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 caseBring thisOriginal product photos, an enabled video template and the applicable AI allowance.
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.
Choose the product and video template in New Campaign, generate AI content, inspect the palette and words, then render after your review.
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 caseBring thisOriginal product photos, a compatible video template and destinations that support your requested first comment.
@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.
Review the complete caption, first comment and on-screen wording separately. After approving a render, watch the actual video before approving delivery.
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 caseChoose supported formats and complete provider-specific settings without silently adding destinations or changing defaults.
Bring thisConnected accounts and a proposed text, image, video, or Story format.
@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.
Approve the eligible destination set and complete its required settings.
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 caseBring thisA connected Pinterest account and an image or video draft.
@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.
Choose a returned board, review the Pin details, and approve delivery separately.
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 caseBring thisA connected TikTok account and a supported image or video draft.
@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.
Complete the account-specific form, then return to the same reviewed post.
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 caseBring thisA finished vertical video with all visible words already inside it and Story-capable accounts.
@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.
Inspect the saved Story draft and explicitly approve its delivery time.
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 caseBring thisAn eligible Meta account, a compatible draft, and the intended collaborator details.
@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.
Confirm the supported collaboration settings, then approve the post separately.
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 caseKeep drafts, explicit publishing approval, saved schedules, and confirmed delivery as distinct steps.
Bring thisApproved content and any media required by the selected format.
@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.
Approve this unchanged draft and name whether to publish now or schedule it.
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 caseBring thisA final reviewed draft and completed delivery settings.
@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.
Check that campaign once for per-account outcomes and confirmed post links.
Good to knowAccepted or queued means the request entered delivery. Only a confirmed destination result supports a published claim.
Link to this use caseBring thisA reviewed draft, completed settings, and a future delivery time.
@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.
Read back the saved local time and destinations, then check delivery after the scheduled time.
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 caseBring thisApproved assets or selected catalog products, account names, dates, and a timezone.
@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.
Approve the whole unchanged plan explicitly, then read back accepted items and any remaining drafts.
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 caseBring thisA connected Facebook Page or Instagram professional account, recent posts and your publishing timezone.
@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.
In New Campaign, select your accounts and click Suggest posting times. Choose a suggestion to fill the campaign schedule, then review before launching.
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 caseBring thisA confirmed workspace and brand, exact destination accounts, an approved post and usable history for the reference account.
@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.
Review the saved date, timezone, media and destinations, then approve scheduling through the normal workflow.
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 casePrepare reviewable product-copy and blog proposals, then deliver only to platforms and permissions that support the action.
Bring thisA Shopify workspace, or a verified WooCommerce connection exposing product-description rewrite support.
@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.
Review the proposal and explicitly approve applying that exact version.
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 caseBring thisA workspace with product-description rewrite support and exact product selections.
@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.
Approve the exact proposals you want applied and inspect each resulting product.
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 caseBring thisA workspace with supported Shopify, Wix, or WordPress blog access and the required permissions.
@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.
Review the proposal, then request the exact destination and draft delivery if wanted.
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 caseBring thisA reviewed current proposal, a supported destination, and permission to write or publish.
@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.
Read back the platform status and returned article URL before treating delivery as finished.
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 caseInspect real delivery outcomes, manage eligible future work, and delegate only within explicit limits.
Bring thisCampaign references from an accepted publish or schedule request.
@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.
Open confirmed public links where available or inspect the specific account requiring attention.
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 caseBring thisA campaign scheduled in the future that has not begun processing.
@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.
If it is eligible, explicitly ask FeedX to cancel that exact campaign and verify the result.
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 caseBring thisA campaign or post showing failed, unstarted, or uncertain delivery.
@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.
Authorize only the exact eligible retry after excluding a duplicate-post risk.
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 caseBring thisAn accessible workspace with the required capabilities and a defined delegation goal.
@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.
Approve the exact plan if wanted, then inspect its status; pause or revoke that named plan when needed.
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 caseMake it your own
You do not need to know tool names. Give the assistant enough context to make a useful first draft.
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
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.
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.
“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.
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.
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.
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.