Webhooks and Blotato: what you can trigger, what you cannot, and what to do instead
Short answer: Blotato, a software subscription that publishes posts to 11 social networks, has no documented webhook that tells you a post was published or failed. Its documentation points you to checking the post by its submission ID. It does have two other webhook features: a publish target that sends post content to your web address, and a webhook that fires after an Instagram DM automation (an automatic reply to a comment or message on Instagram, the photo and video app) sends. Webhooks that start your own workflow come from n8n, Make or Zapier, not from Blotato.
A common question is whether Blotato can call you back when a post goes live. The plain answer is no, and this page shows what to use instead.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A webhook is a web address on your side that another service calls when something happens, so you do not have to keep asking. Many tools offer them. Blotato offers two narrow ones, and not the one people want most. This guide says what exists, what does not, what to do instead in n8n, Make and Zapier, and how to confirm the answer yourself. A submission ID is the code Blotato returns when you create a post, and it is what you use to look the post up.
This page may contain affiliate links from which Blur Studio earns commissions.
What exists today, in one table
| Event or need | Blotato webhook? | What to use |
|---|---|---|
| Post published | None documented | Check status by submission ID. |
| Post failed | None documented | Check status by submission ID. |
| Send post content to your own URL | Yes, a publish target called webhook (REST only) | See below. |
| Instagram DM automation sent a message | Yes, a webhook on the automation | See below. |
| Start a workflow when a new row, email or RSS item arrives | Not Blotato's job | Your automation tool's trigger. |
| Account-wide events (new follower, new comment) | None documented | Poll the comments or messages calls. |
"None documented" matters. Blotato's help pages for publishing and status describe no webhook or callback for post outcomes. The way to learn the outcome is the status call. This is what the documentation says, not a claim that Blotato's team could never add one. Ask support and keep the reply (the test plan is below). Many buyers expect push notifications from a posting tool, so the question is worth putting to support.
Webhook feature 1: the publish target
In Blotato's REST publish request, you can set the platform to other and the target type to webhook with a url. Blotato then sends the post content to your address, instead of a social network. Blotato's reference says this is reserved for custom webhooks and "does not subscribe you to account-wide events". It is not available through the MCP tool blotato_create_post, which is the connection method AI assistants use. The shape is:
{
"post": {
"accountId": "YOUR_ACCOUNT_ID",
"content": {
"text": "Text to send to your webhook",
"mediaUrls": [],
"platform": "other"
},
"target": {
"targetType": "webhook",
"url": "https://example.com/your-webhook-address"
}
}
}
Open questions to test, because the pages read do not answer them: which ID the webhook target expects in accountId (the field table lists it as required for every post), what exact body your address receives, whether there is a signature you can verify, and how Blotato retries if your address is down. Send a test to a request-catching service and look at what arrives before you build on it. A good use is "send this approved post to my own system" (for example a Slack message or a database) from a workflow that already uses Blotato for networks.
Webhook feature 2: DM automations
Blotato's Instagram and Facebook DM automations (comment-to-DM replies) have an optional webhook object. After the DM is sent, Blotato calls your address with a body like this:
{
"email": "person@example.com",
"isFollower": true
}
You choose the method (GET, POST, PUT, PATCH or DELETE) and a public URL, and can add headers. Every method except GET carries the JSON body. isFollower can be true or null, and email is null when Blotato holds none. The email field comes from the email gate if you use one. Blotato's docs say it waits 15 seconds for your endpoint, does not retry, and does not follow redirects. Also: the webhook is not called if a public comment reply fails the run, and the webhook, follow gate and email gate carry no extra charge or credits. A common use is lead capture: the webhook adds the email to your list or sheet. Treat the incoming data as untrusted input and be careful with personal data, since collecting email addresses brings privacy rules. See Blotato Instagram DM automation.
What to do instead: poll the status
Polling means you ask repeatedly, with limits. It is the documented route, and it works in every automation tool.
- Create the post. Save
postSubmissionIdfrom the 201 response straight away. - Wait at least 10 seconds. Blotato asks for that gap between status requests.
- Call
GET https://backend.blotato.com/v2/posts/{postSubmissionId}with the headerblotato-api-key. It allows 60 requests a minute. - Read the status:
in-progress(ask again),scheduled(queued, stop),published(readpublicUrl), orfailed(readerrorMessage). - Set a cap, such as 12 checks, and report the ID if you reach it.
The full pattern, with a script and retry rules, is in fix silent failures. For many pending posts, the list call (GET /v2/posts, with status and date filters) shows scheduled, published and failed posts at once, at 60 requests a minute. An MCP assistant makes the same calls, and they count against the same limits.
How n8n, Make and Zapier each handle it
- n8n (a workflow automation tool). Use the Blotato node's Post, Get operation in a loop with a Wait node and an attempt counter. For things that happen outside Blotato, n8n's Webhook node starts a workflow. The Wait node can also pause until a web address is called, and has a Limit Wait Time setting, and its webhook resume supports an IP allowlist. Do not wire a Blotato callback into that, since Blotato sends none.
- Make (a similar tool). Blotato's Make app has actions and no triggers, so a Blotato event cannot start a Make scenario. Start with a schedule, a custom webhook or another app's trigger. Make queues incoming webhooks when credits run out (a queue of 667 per 10,000 credits licensed, up to 10,000). For a status loop, check whether your Blotato module has a status lookup, and otherwise use Make's HTTP module with the REST request.
- Zapier (a third tool). Blotato has no official Zapier app, so use Webhooks by Zapier to send the requests with the
blotato-api-keyheader. Zapier's Catch Hook trigger gives you an address to receive webhooks from other services, and Zapier says that address is protected only by being hard to guess, so do not make it public. Webhook actions are listed among Professional features on Zapier's pricing page, so check your plan.
Costs depend on how many status checks you run. See the automation cost calculator.
Limits to plan around
- The API and MCP need a paid Blotato plan. Generating an API key ends the 7 day trial and starts a paid plan. Starter is $29 a month billed monthly as of November 2026 (plans are on Blotato's site).
- Create post: 30 requests a minute. Status and list calls: 60 a minute. Polling many posts at once can reach that, so spread checks out.
- Webhook target and slot management are REST only, not in the MCP tools.
- No delivery guarantee is documented for webhook calls, so do not make a payment or a legal record depend on one.
- The documented states are only
in-progress,scheduled,publishedandfailed. A wrong ID returnsin-progress.
Test plan: confirm it yourself and ask support
| Test | Pass | Fail |
|---|---|---|
| Ask Blotato support: "Is there a webhook or callback for post published or post failed, or a plan to add one?" Save the reply and date. | You have a written answer. | No answer within a week, so assume none. |
| Send one post with the webhook target to a request-catching address. | You see the exact body and headers. | Nothing arrives or you cannot tell what it is. |
| Turn your receiving address off, send again, turn it on. | You learn whether Blotato retries the publish target (the DM webhook is documented as not retried). | Posts are lost and you were not told. |
| Poll a published post with your loop. | Status published with a public URL. | Loop never ends. |
| Poll a fake ID. | Your loop stops at its cap. | Your workflow reports success. |
Use this support message as a start: "Hello, I use the REST API on a paid plan. Does Blotato offer any webhook or callback that fires when a post is published or fails? If not, is the recommended approach to poll GET /v2/posts/{id}? Thank you." Record date, reply, and who answered. Blotato's support is mostly an in-app chat, with no published response time, so allow time.
Who should skip Blotato for this reason
If your design needs push notifications from the posting tool for every event, such as a downstream system that must react in seconds, Blotato's current design (polling) is a poor fit. Look at tools with outbound webhooks, and read alternatives for agents and APIs. If you post a few times a day, polling every 10 seconds for a minute costs nothing, and the lack of webhooks does not matter.
How this page was checked
The facts come from Blotato's publish-post, get-post and rate-limit references, its DM automation documentation, its pricing page, and the help pages of n8n, Make and Zapier. Last checked 21 November 2026, refreshed every 90 days. Blur Studio has not run Blotato itself, so the test plan is for you to run. Blotato may add webhooks later, so check its current documentation.
How I'd approach this
Assume there is no callback and build the polling loop first, because it works today. Day 1: send the support question. Day 2: build create, wait, check, with a cap. Day 3: log the status and URL. Day 4: test the fake ID case. If support later confirms a webhook, replace the loop and keep the daily check. A free AI brainstorm call can help you choose tools, and the free AI tools are open to use.
Questions people ask
Does Blotato have webhooks?
Two narrow ones: a REST publish target that sends post content to your URL, and a webhook on Instagram DM automations. It has no documented webhook for post published or post failed.
How do I know when a Blotato post is live?
Save the submission ID, wait at least 10 seconds, then call the get-post endpoint until the status is published or failed, with a cap on attempts. See post stuck on processing.
Can a Blotato event start a Make scenario?
Not directly. Blotato's Make app has actions only, no triggers. Use a schedule, a custom webhook or another app as the trigger.
Can I use webhooks with the MCP connection?
The webhook publish target is REST only. It is not available through the MCP tool blotato_create_post. See Blotato API and MCP.
What does the DM automation webhook send?
An email field and an isFollower value, after the DM sends. It is not called if a public comment reply fails the run, and it has no extra charge.
Is the Zapier Catch Hook address secure?
Zapier describes it as protected by being hard to guess, so keep it private. Zapier's pricing page lists webhooks among Professional features, so check your plan before building.
Will Blotato add post status webhooks?
Unknown. Ask support, record the reply, and check the documentation again in a few months. Do not build on a feature that is not documented.
More in this topic: Social media: automation with n8n, Make and Zapier (27 guides) →