Start free

Social media automation recipes

Pick your automation tool and what should start a post. Each recipe gives the steps, the exact PostBoost API calls, and for n8n a workflow you can import.

8 recipes. Last verified:

RSS feed to the PostBoost queue

New blog post (RSS)

Each new blog post goes into the next free slot of your posting schedule with its title and link.

Built in: RSS auto-post. PostBoost can watch an RSS feed and turn new items into drafts or queued posts by itself, with no automation tool: add the feed on the Recycling & RSS page (RSS feeds tab) or with the API.

How it works

Steps in n8n

  1. RSS Feed Trigger: your feed URL, poll every hour.
  2. HTTP Request: POST /{workspaceUuid}/posts with your accounts, the item title and link as the text, the link as the card URL, and "queue": true.
  3. In PostBoost, set your queue times (Queue → Posting Schedule): each item takes the next free slot.

Steps in Zapier

  1. Trigger: RSS by Zapier → New Item in Feed.
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Data: accounts, versions (the item title and link as the text) and "queue": true.

Steps in Make

  1. Trigger: RSS → Watch RSS feed items.
  2. Action: HTTP → Make a request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>. Body type Raw, content type JSON.
  4. Request content: accounts, versions (the item title and link as the text) and "queue": true.

API calls: createPost

RSS feed to AI caption drafts

New blog post (RSS)

Each new blog post becomes a draft with one AI-written caption per account, ready for you to review. Uses PostBoost AI credits, no third-party AI.

Built in: RSS auto-post. PostBoost can watch an RSS feed and turn new items into drafts or queued posts by itself, with no automation tool: add the feed on the Recycling & RSS page (RSS feeds tab) or with the API.

How it works

Steps in n8n

  1. RSS Feed Trigger: your feed URL, poll every hour.
  2. HTTP Request: POST /{workspaceUuid}/ai/blog-to-social with the item link as "url", your account IDs and "create_post": true.
  3. In PostBoost, review the drafts and schedule the ones you like.

Steps in Zapier

  1. Trigger: RSS by Zapier → New Item in Feed.
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/ai/blog-to-social.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Data: "url" (the item link), "account_ids" and "create_post": true.

Steps in Make

  1. Trigger: RSS → Watch RSS feed items.
  2. Action: HTTP → Make a request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/ai/blog-to-social.
  3. Headers: Authorization: Bearer <your token>. Body type Raw, content type JSON.
  4. Request content: "url" (the item link), "account_ids" and "create_post": true.

API calls: blogToSocial

Google Sheets rows to scheduled posts

Spreadsheet or content calendar row

Plan posts in a sheet (date, time, text, account IDs) and schedule every row in one run.

Steps in n8n

  1. Manual Trigger: run it when the sheet is ready.
  2. Google Sheets → Get Row(s): your sheet with the columns date, time, text, account_ids.
  3. HTTP Request: POST /{workspaceUuid}/posts per row with "schedule": true, the row date and time, and your time zone.

Steps in Zapier

  1. Trigger: Google Sheets → New Spreadsheet Row.
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the row text), "schedule": true, "date" (YYYY-MM-DD), "time" (HH:MM) and "timezone".

Steps in Make

  1. Trigger: Google Sheets → Watch New Rows.
  2. Action: HTTP → Make a request (body type Raw, JSON), method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the row text), "schedule": true, "date" (YYYY-MM-DD), "time" (HH:MM) and "timezone".

API calls: createPost

Airtable content calendar to scheduled posts

Spreadsheet or content calendar row

Every 15 minutes, rows marked Ready are scheduled in PostBoost and the post UUID is written back to the row.

Steps in n8n

  1. Schedule Trigger: every 15 minutes.
  2. Airtable → Search: rows where {Status} = 'Ready'.
  3. HTTP Request: POST /{workspaceUuid}/posts with "schedule": true, the row's Publish At split into date and time (UTC), and an Idempotency-Key header per row.
  4. Airtable → Update: set Status to Scheduled and save the returned uuid in Post UUID.

Steps in Zapier

  1. Trigger: Airtable → New or Updated Record (view filtered to Status = Ready).
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the row text), "schedule": true, "date" (YYYY-MM-DD), "time" (HH:MM) and "timezone".
  5. Action: Airtable → Update Record: Status = Scheduled, Post UUID = the uuid from the response.

Steps in Make

  1. Trigger: Airtable → Search Records (formula {Status} = 'Ready'), scheduled every 15 minutes.
  2. Action: HTTP → Make a request (body type Raw, JSON, parse response), method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the row text), "schedule": true, "date" (YYYY-MM-DD), "time" (HH:MM) and "timezone".
  5. Action: Airtable → Update a Record: Status = Scheduled, Post UUID = the uuid from the response.

API calls: createPost

Google Drive video to Reels, TikTok and Shorts drafts

New file in a cloud folder

Drop a video in a Drive folder and get one draft for Instagram, TikTok and YouTube with the video attached and the file name as the caption.

Steps in n8n

  1. Google Drive Trigger: file created in your folder, poll every minute.
  2. Google Drive → Download: the new file (binary field "data").
  3. HTTP Request: POST /{workspaceUuid}/media as multipart form data, the binary in the field "file".
  4. HTTP Request: POST /{workspaceUuid}/posts with your Instagram, TikTok and YouTube accounts and the returned media ID; no "queue" or "schedule", so it stays a draft.

Steps in Zapier

  1. Trigger: Google Drive → New File in Folder (share the folder with "Anyone with the link" so PostBoost can fetch the file).
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/media/remote/initiate.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): "url" (the file's download link).
  5. Large files download in the background: the response has a "download_id". Add Delay by Zapier, then one GET /{workspaceUuid}/media/remote/{download_id}/status; if "status" is not yet "completed", repeat the Delay and the check.
  6. Action: Webhooks by Zapier → Custom Request, POST /{workspaceUuid}/posts with accounts, versions (the file name as the text, the media ID in "media"); no "queue" or "schedule", so it stays a draft.

Steps in Make

  1. Trigger: Google Drive → Watch Files in a Folder.
  2. Google Drive → Download a File.
  3. HTTP → Make a request: POST https://postboost.co/app/api/{workspaceUuid}/media, body type Multipart/form-data, field "file" of type File.
  4. HTTP → Make a request: POST /{workspaceUuid}/posts with accounts, versions (the file name as the text, the media ID in "media"); no "queue" or "schedule", so it stays a draft.

API calls: uploadMedia initiateRemoteUpload getRemoteUploadStatus createPost

Approve posts in Slack before they go out

Post request that needs approval

A new post request becomes a draft, Slack asks for approval, and the post joins the queue only when someone approves it.

Steps in n8n

  1. n8n Form Trigger: one "Text" field for the post.
  2. HTTP Request: POST /{workspaceUuid}/posts with your accounts and the text, no "queue" or "schedule" (a draft).
  3. Slack → Send and Wait for Response: approve or decline buttons in your channel.
  4. If approved: HTTP Request POST /{workspaceUuid}/posts/add-to-queue/{uuid}. If declined: HTTP Request DELETE /{workspaceUuid}/posts/{uuid} with "trash": true.

Steps in Zapier

  1. Trigger: the app where requests arrive (for example a form or a Slack message).
  2. Action: Webhooks by Zapier → Custom Request, method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the request text); no "queue" or "schedule", so it stays a draft.
  5. Your approval step (for example a Slack message that waits for a reply).
  6. Approved: Webhooks by Zapier → POST /{workspaceUuid}/posts/add-to-queue/{uuid}. Declined: DELETE /{workspaceUuid}/posts/{uuid} with "trash": true.

Steps in Make

  1. Trigger: the app where requests arrive (for example a form or a Slack message).
  2. Action: HTTP → Make a request (body type Raw, JSON, parse response), method POST, URL https://postboost.co/app/api/{workspaceUuid}/posts.
  3. Headers: Authorization: Bearer <your token>, Content-Type: application/json.
  4. Body (JSON): accounts, versions (the request text); no "queue" or "schedule", so it stays a draft.
  5. Your approval step, then a Router: approved → HTTP POST /{workspaceUuid}/posts/add-to-queue/{uuid}; declined → HTTP DELETE /{workspaceUuid}/posts/{uuid} with "trash": true.

API calls: createPost addPostToQueue deletePost

Slack alert when a post fails to publish

PostBoost event (webhook)

PostBoost calls your workflow the moment a post fails on an account, and your team sees the network's error in Slack.

Steps in n8n

  1. Webhook node: method POST, path postboost-failed. Copy its production URL (it must be public https://).
  2. Run the "Subscribe once" branch: HTTP Request POST /{workspaceUuid}/webhooks/subscriptions with that URL and the event post.publishing_failed.
  3. Slack → Send Message: the account name, network and first error from the delivery.

Steps in Zapier

  1. Trigger: Webhooks by Zapier → Catch Hook. Copy the hook URL.
  2. Once: POST https://postboost.co/app/api/{workspaceUuid}/webhooks/subscriptions with "callback_url" (the hook URL) and "events": ["post.publishing_failed"].
  3. Action: Slack → Send Channel Message with data.account.name, data.account.provider and data.account.errors.

Steps in Make

  1. Trigger: Webhooks → Custom webhook. Copy the hook URL.
  2. Once: POST https://postboost.co/app/api/{workspaceUuid}/webhooks/subscriptions with "callback_url" (the hook URL) and "events": ["post.publishing_failed"].
  3. Action: Slack → Create a Message with data.account.name, data.account.provider and data.account.errors.

API calls: createWebhookSubscription

Weekly social analytics digest in Slack

On a schedule

Every Monday at 9:00 your channel gets last week's followers, growth, posts, best account and the account that needs attention.

Steps in n8n

  1. Schedule Trigger: weekly, Monday at 9:00.
  2. HTTP Request: GET /{workspaceUuid}/analytics?period=last_week.
  3. Slack → Send Message: data.total_followers, data.follower_growth, data.total_posts, data.best_account.name.

Steps in Zapier

  1. Trigger: Schedule by Zapier → Every Week, Monday 9:00.
  2. Action: Webhooks by Zapier → GET https://postboost.co/app/api/{workspaceUuid}/analytics?period=last_week, header Authorization: Bearer <your token>.
  3. Action: Slack → Send Channel Message with the summary fields.

Steps in Make

  1. Schedule the scenario: every week, Monday 9:00.
  2. HTTP → Make a request: GET https://postboost.co/app/api/{workspaceUuid}/analytics?period=last_week, header Authorization: Bearer <your token>, parse response.
  3. Slack → Create a Message with the summary fields.

API calls: getAnalyticsSummary

Runs in your browser. Nothing you type is sent to PostBoost.

Use this tool from code

The same tool is a free API call, no account needed. It also works with our 9 SDKs and the MCP server.

curl 
curl 'https://postboost.co/app/api/tools/social-media-automation-recipes?platform=zapier&trigger=rss'

API docs for this tool SDK quickstart

Last verified:

Sources:

Most people who want to automate social media posting already have the trigger: a blog with an RSS feed, a content calendar in Google Sheets or Airtable, a Drive folder of videos, or a team that approves posts in Slack. What is missing is the step that turns that trigger into a scheduled post on every network.

These recipes fill that gap with the PostBoost REST API. Each one works with the generic HTTP step that n8n, Zapier and Make already have: HTTP Request in n8n, Webhooks by Zapier in Zapier and HTTP in Make. You send one request with your API token, and PostBoost publishes to Instagram, LinkedIn, X, TikTok, YouTube, Facebook and the other networks you connected.

Every recipe lists:

  • The steps for the platform you picked, in the order you add them.
  • The API calls it makes, each linked to its page in the API reference.
  • An n8n workflow you can copy or download and import as it is. It uses only n8n's built-in nodes, so you do not need a community node.

Some goals need no automation tool at all. PostBoost turns new RSS items into drafts or queued posts and brings evergreen posts back on a schedule by itself; the recipes say so when that is the case, and the Automations docs explain how. The Zapier and Make docs list every endpoint the platforms can call.

Start with the recipe closest to your workflow, then change the trigger or the text. When a post fails, the failure alert recipe tells your team in Slack with the network's error, so nothing goes missing quietly.

How to use

  1. Pick your platform: n8n, Zapier or Make.
  2. Pick a trigger, such as a new blog post, a spreadsheet row or a schedule.
  3. Follow the steps. Each one names the platform's generic HTTP step and the PostBoost API call it makes.
  4. On n8n, copy or download the workflow, import it, and add your API token as a Header Auth credential.

FAQ

Do I need Zapier to post an RSS feed?

No. PostBoost watches RSS and Atom feeds itself and turns new items into drafts or queued posts, so you need no automation tool for that. Use a recipe only when you want extra steps, such as AI captions per account.

Is there a native PostBoost app for Zapier, Make or n8n?

The PostBoost apps for Zapier and Make are built and pending review, so they are not in either app directory yet. Every recipe here uses the generic HTTP step that each platform already has, including n8n's HTTP Request node, so it works today.

What do I need to run a recipe?

A PostBoost account, an API token (your avatar → Access Tokens), your workspace UUID from the dashboard URL, and the IDs of the accounts you post to. The API is on every plan, including the free plan, with no per-call fees.

Can I schedule posts from a spreadsheet?

Yes. The Google Sheets and Airtable recipes read rows with a date, time and text and schedule each one through the API. An Idempotency-Key header per row stops a retried run from scheduling the same row twice.

How do I get told when a post fails?

Subscribe your automation's webhook URL to the post.publishing_failed event. PostBoost then sends one delivery per failed account, with the network's error, and signs each delivery so you can verify it.

Can an AI agent use these recipes?

Yes. The same recipes are on the free PostBoost API and on our MCP server as `find-automation-recipes`, filtered by platform, trigger or search text.

Related

Social media API request builder

Build a create-post request for the PostBoost social media API and copy it as curl, Python, Node.js, PHP, Go, Ruby, Java, C#, Rust or the CLI.

Webhook signature verifier (HMAC)

Check an HMAC webhook signature against the raw body and secret in your browser. SHA-256, SHA-1 or SHA-512, hex or base64, with hints when it fails.

MCP server config generator for social media

Get the exact MCP setup to connect Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex, Gemini CLI or n8n to PostBoost's social media MCP server.

How to Schedule Social Media Posts with Claude

Connect Claude to PostBoost over MCP, then draft, check and schedule posts for LinkedIn, X, Instagram and more from a chat. Setup takes about two minutes.

Automations

Add an RSS feed and new articles become drafts or queued posts.

API and webhooks

Publish and schedule to 15 channels through one REST API, nine SDKs, webhooks and a hosted MCP server.

Try PostBoost free

API, webhooks and MCP on every plan, including Free. No credit card required.

Start free Read the quick start