Zapier + PostOnce
Turn RSS updates into social drafts
Save feed updates as PostOnce drafts with Zapier. Review the text before choosing where and when to publish.
A Zapier account and a PostOnce plan with API access. Connect through our private app invitation; this app is not listed or approved in Zapier’s public directory.
Set up your connection
Connect Zapier to PostOnce
Use the private app invitation and save your key in a Zapier connection.
- 1
Accept the PostOnce invitation
Open the private app invitation while signed in to Zapier, accept it, then select PostOnce in your Zap’s action step.
Accept PostOnce invitationZapier shows that this private app has not been reviewed or approved. You do not need to install a developer package or import a workflow file.
- 2
Save a dedicated API key
Create a PostOnce API key with
Create an API keyaccounts:readfor the connection test andposts:writeplusposts:readto create and inspect drafts.In Zapier, connect a PostOnce account and enter the key in the private API Key field. Keep it out of RSS fields, action content and shared screenshots. An empty social account list is valid; the first draft needs no destination accounts.
- 3
Test one reviewable draft
Test Create Draft with a feed item, then open the returned draft in PostOnce. An inbox result means it was saved for review, not published.
Follow the field mapping below. Test the action before turning on your Zap, then check Zapier’s run history once activated. Connecting the app or testing an action does not activate the automation.
From a feed item to a draft you can review
Start with RSS → Create Draft
1. RSS by Zapier
Choose your feed
Select New Item in Feed, enter your feed URL, and test the trigger to load an actual item.
2. PostOnce · Create Draft
Save the text
Map the stable source key and title plus article link below. Leave destination accounts and media empty for this first draft.
3. PostOnce
Review the returned draft
Inspect the returned ID and inbox status. Optionally use that ID in Find Draft by ID; review the draft before publishing.
| PostOnce field | Map from your feed item |
|---|---|
| Source Event Key | rss-draft:your-feed: followed by the item’s immutable GUID. Use a stable article URL if the feed has no GUID. Keep the complete key within 200 characters. |
| Final Content | The item’s title, a line break, and its article link. |
Keep the feed prefix fixed and reuse the same key and content when retrying the same item. Do not use a timestamp or generate a new key to bypass an uncertain result. A changed-content conflict needs investigation. Rotating the API key changes deduplication scope, so inspect existing drafts before replaying older items.
Review drafts in PostOnceBuild on the first draft
Publish approved content
Use Create Post only after choosing connected destination accounts and approving the final content. Add Delay by Zapier, then Find Post by ID using the ID returned by creation. Check each destination: queued does not mean delivered.
Prepare crossposting
Use Create Crossposting Workflow with supported connected source and destination accounts. Keep the workflow inactive while reviewing it. Add the required workflow scopes to your key; creating a workflow does not publish a source post.
For media actions, use a supported public media URL and check destination requirements. A local path or chat attachment is not an uploaded file. The text-only RSS recipe needs no media.
Questions before connecting
Is this in Zapier’s public directory?
Use the private invitation above. The native app can be connected and tested, but public directory approval and shared Zap templates are separate milestones.
Will testing publish to social accounts?
Create Draft saves content in your inbox without publishing. Review the draft in PostOnce before selecting destinations or scheduling.
What if a retry fails or returns a conflict?
Inspect the earlier draft using its returned ID and keep the same source key for unchanged input. Do not create a fresh key merely to retry an uncertain write.
How do I disconnect?
Turn off Zaps that use this connection, remove the PostOnce connection in Zapier, and revoke its dedicated API key in PostOnce Preferences. Preserve unrelated connections and keys.
Explore more ways to connect
Claude Code
Coding tools
Turn a product update into social posts from your terminal. Connect Claude Code to the accounts and crossposting workflows you manage in PostOnce.
View setupCodex
Coding tools
Ask Codex to publish your release update to connected social accounts, then inspect each destination’s result through PostOnce.
View setupCursor
Coding tools
Keep your product update in the editor. Use Cursor’s agent to publish through PostOnce and manage automatic crossposting between connected accounts.
View setupOpenClaw
AI agents
Connect your OpenClaw agent to PostOnce to publish updates, check delivery, and manage automatic crossposting from your connected accounts.
View setupHermes Agent
AI agents
Use Hermes Agent to publish updates through PostOnce, check delivery, and manage automatic crossposting between your connected accounts.
View setupn8n
Workflow automation
Publish approved content from n8n to your connected social accounts. Check each destination’s result in the same workflow.
View setupMake
Workflow automation
Turn RSS updates into PostOnce drafts with Make. Review the text before choosing where and when to publish.
View setupAny MCP client
MCP clients
Connect an MCP-compatible agent to PostOnce to discover your social accounts, publish posts, and set up automatic crossposting.
View setupYour next post starts here.
A Zapier account and a PostOnce plan with API access. Connect through our private app invitation; this app is not listed or approved in Zapier’s public directory.