Blotato n8n or Make error codes and what they mean
Short answer: Blotato, a software subscription that writes, schedules and publishes social media posts, can also be driven by n8n and Make, two tools that connect apps and run automatic steps. When a step fails, you usually see a 429 (too many requests in a minute), a numbered Blotato code such as 5000, 20005 or 20101, or a plain message such as an empty or non-public media link. This page maps each to a cause and a fix, and says how to retry without posting twice.
Your n8n or Make run stopped with an error from Blotato. Here is a table of the ones Blotato documents, what causes each and what to do.
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.
An error code is a short number or message a service sends back when it refuses or fails a request. Blotato publishes limits and a list of API error messages in its help centre. It does not publish a single numbered list for every error, so this page groups what is documented as of November 2026 and tells you what to log so you can ask support about the rest. An API, short for application programming interface, is the official doorway your n8n or Make step uses to send a post to Blotato.
This page may contain affiliate links from which Blur Studio earns commissions.
Before you start: three basics
- API key. n8n and Make need a Blotato API key, made under Settings, then API. Blotato's pricing page and help say that creating an API key ends the free trial at once and starts a paid plan (Blotato says the plan activated is Starter, $29 a month, billed monthly, as of November 2026, with a confirmation pop-up first). Do not make a key on a test account unless you are ready to pay.
- Base address and header. The REST address is backend.blotato.com/v2 and the key goes in a header called blotato-api-key. A wrong key is the first thing to rule out.
- Publishing is two steps. A post request returns a submission ID quickly. The post is then published in the background. You poll the status until it says published or failed. A success from the first call does not mean the post is live.
The error table
| You see | What it means | Fix |
|---|---|---|
| 429, too many requests | You sent more requests per minute than the route allows. See the limits table below. | Slow down, wait out the minute, retry. Space calls out. |
| Wrong or missing API key | The key is not valid for this account or is not in the header. | Copy the key again from Settings, then API. Check for stray spaces. |
| 5000, account not found | The account ID you sent does not exist in this Blotato account. | List your accounts through the node or API and copy the ID from there. |
| Wrong Page ID | Facebook needs both the account ID and the Page ID, and the Page ID sent is not valid. Pinterest likewise needs a board ID. | In Blotato, use the Copy Page ID button for the Facebook Page and paste it in. Re-read the board ID for Pinterest. |
| 20005, text too long | The text is over the platform's limit. Blotato says emoji and full-width characters count as 2. | Shorten the text. Re-count with emoji doubled. |
| 20101, active contact limit | You reached the monthly count of people your account can reply to in DM and comment automation (1,000 on Starter, 6,000 on Creator, 15,000 on Agency). | Wait for the monthly reset, or move up a plan. |
| URL is empty | The media link field was blank, often because an earlier step returned nothing. | Check the earlier step's output. Make the step stop if the link is empty. |
| Invalid file format or media conversion failed | The file type is not accepted for that platform, or Blotato could not convert it. | Use MP4 with H.264 video and AAC audio. Re-export and try again. |
| Media URL not reachable | The link needs a login, has expired or is not public. Blotato needs a public link without sign-in. | Use a public link. Test it in a private browser window. |
| Out of credits | An AI image or video step needs more credits than your balance, judged on the whole job. | Top up or pick a cheaper model. See what to buy when Blotato says out of credits. |
| Maximum number of scheduled posts | Your queue cap is full: 200 Starter, 1,000 Creator, 3,000 Agency. | See how to clear queue space. |
| Scheduled more than 9 months ahead | The schedule time is past the horizon Blotato's help gives. | Pick a nearer date. |
| Schedule time rejected | The scheduled time must carry a UTC offset. Without it, Blotato cannot read it as a time. | Send an ISO time with an offset, for example 2026-12-01T09:00:00-05:00. |
| 500 on visual creation | A server-side failure while making an image or video. | Check the status of the visual before you retry. Credits are only taken on success. |
Messages for a platform's own rules also come back from Blotato. Examples from its help: Instagram needs at least one image or video, Threads takes one image or video per post, and TikTok needs a privacy level and several yes-or-no declarations. For those, see the platform pages, for example fixing a failed Instagram post.
Rate limits, 429 and retry timing
Blotato's rate-limits page, read 21 November 2026, lists limits per minute for most routes. A 429 means you passed the limit for that route.
| Route | Limit |
|---|---|
| Create a post | 30 a minute |
| Read posts and check post status | 60 a minute |
| Upload media | 30 a minute, and 120 a minute for presigned uploads |
| Post comments | 30 a minute to post, 60 to read |
| Messages | 30 a minute to send, 60 to read |
| DM automation | 30 a minute to write, 60 to read |
| Pinterest boards | 45 a minute |
| Buy credits (API) | 10 an hour |
The limits are per minute, so the retry time that makes sense is the next minute. Blotato says to wait for the retry interval when the response supplies one, then lower how often you call before you resume. Do not retry in a tight loop.
A made-up example of the arithmetic: you load 100 posts from a sheet into a loop. The cap is 30 create-post calls a minute, so 100 / 30 = 3.3, which means at least 4 minutes. Send 20 a minute for a margin, and you finish in 5 minutes. In n8n, that means a Wait node or the Loop Over Items node with a pause between batches. In Make, it means a sleep step or a scheduled scenario that sends a fixed number per run.
Retry rules that avoid double posts
- 429 is safe to retry. The request was refused, so nothing was created. Wait a minute, then retry. This is my judgment from how rate limits work. Confirm in your first test.
- Validation errors are not safe to retry unchanged. They fail the same way each time. Fix the field first.
- A failure after the submission ID was returned is a different case. Poll the status. Blotato's guidance is not to retry blindly after an uncertain write.
- Do not trust in-progress forever. Blotato's docs say in-progress is also returned when no record is found. Add a time limit, for example 10 minutes, then send yourself an alert.
- Keep the submission ID and the request ID in a sheet or log. Blotato's Logs page lets you copy the request ID. Support asks for both.
In n8n, the Retry On Fail setting on a node repeats a failing step, but turn it off for the create-post step, or limit it to 429 cases through an error branch, so it does not repeat a post that may have gone through. How you do that depends on your n8n version, so check its docs. In Make, use an error handler on the Blotato module that logs the failure and sends you a message instead of repeating the module. For more on n8n, see n8n for agencies, and for the difference between the two tools, see Zapier vs Make.
What to log on every failure
Copy this into a sheet. A complete row lets support find your post fast.
| Date and time | Tool and scenario name | Blotato step | Full error text or code | Account ID and platform | Media link | Submission ID | Request ID | Status after 10 min |
|---|---|---|---|---|---|---|---|---|
A test plan before you go live
The 7 day free trial does not include the API or MCP, as of November 2026, and creating an API key ends the trial and starts the paid plan. So plan to test on a paid month, on a test account, with a low-stakes post. The results columns are blank for you to fill in.
| Test | Expected if it works | Result | Pass or fail |
|---|---|---|---|
| Send one text post to one account | Submission ID, then published status | ||
| Send with a wrong account ID | An account-not-found style error | ||
| Send a media link that needs a login | A media error | ||
| Ask for the status of one existing post 65 times inside one minute (the limit is 60), so no new post is created | A 429 on the extra calls | ||
| Repeat one status call after a minute | It goes through |
Pass: every row behaves as expected and no post appears twice on the platform. Fail: a duplicate appears, or the status stays in-progress for longer than your alert time.
Support
Blotato's support is the in-app chat button or support@blotato.com, with no published response time. Blotato says Creator and Agency plans include help with troubleshooting n8n and Make automations, and Agency adds dedicated automation support, per its pricing page. On Starter (see Blotato's plans), include the log row above in your first message so nobody has to ask you for it.
Who should skip the automation route
- If you post a few times a week by hand, the web app is simpler and has no API key trap.
- If nobody in your business can read an error log, buy time with a simpler setup first.
- If you need approval before anything is published, this route needs a Slack or email approval step that you build yourself, since Blotato has no approval feature.
How this page was checked
The limits and messages come from Blotato's help centre pages on rate limits, errors, publishing status, API keys and credits, and from its pricing page and llms.txt file, last checked 21 November 2026 and refreshed every 90 days. Blotato does not publish one complete numbered list, so rows cover what is documented. Blur Studio has not run Blotato itself. Test with a paid month on a test account or an equivalent before you rely on the table.
How I'd approach this
Build the workflow small and add one safeguard at a time. Day one: send one post to one account and log the submission ID. Day two: add the status check and an alert for anything not published after 10 minutes. Day three: add spacing so you stay under 30 create calls a minute, and run the five tests above. Day four: add the approval step if people other than you need to see the post. Keep the log sheet for the first month. If you want a second pair of eyes on the plan, a free AI brainstorm call is available, and the free tools at /free may help with the writing side.
Questions people ask
What does a 429 from Blotato mean?
It means you sent more requests per minute than that route allows, for example more than 30 create-post calls. Wait for the next minute and retry, and spread out batches.
Is it safe to retry a 429?
In principle yes, since the request was refused and nothing was created, but confirm in your first test. Do not retry a failure that happened after Blotato returned a submission ID without checking the post status.
What do error codes 5000, 20005 and 20101 mean?
5000 is account not found, 20005 is text too long (emoji count as 2), and 20101 is the monthly active-contact limit for DM and comment automation. These are the ones Blotato documents in its help.
Why does Blotato say my media URL is not valid?
Blotato needs a public link that works without signing in. Links that expire, need a login or are empty fail. Test the link in a private window and use MP4 with H.264 video and AAC audio for video.
Does Blotato work with Zapier?
Blotato has official nodes for n8n and Make. It can also take a webhook, a web address one tool calls to trigger another, so other tools can reach it. See Blotato vs Zapier and check Blotato's current integration list.
Why did my post stay in progress?
Blotato's docs say in-progress is also returned when no record is found, so it does not prove the post is being worked on. Set a time limit, check the post in Blotato's Posts and Logs, and send support the request ID.
Does the free trial work with the API?
No. The trial excludes the API and MCP, and creating an API key ends the trial and starts the paid plan, according to Blotato's pricing page and help. Check the confirmation pop-up before you make a key.
More in this topic: Social media: posting limits and fixes by platform (40 guides) →