How to monitor a social media automation: alerts, logs and a 5 line weekly check
Short answer: An automation that posts for you needs a small amount of watching, because the usual failure is silence: the run says success and nothing was posted. Log one row for every post, set alerts for failures and stuck rows, and do a 5 line check once a week: failed posts, stuck statuses, credit balance, queue size and rate limit errors. Blotato, a software subscription that schedules and publishes social media posts, has no webhook that pushes a failure to you, so you ask it on a timer.
Your posting automation is live and you want to know the cheapest way to find out when it breaks, before a customer or a gap in your calendar tells you.
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.
Most automations fail quietly. A key expires, a media link dies, a platform rejects a caption, or a run stops halfway. The lesson: "the run succeeded" and "the post is live" are different facts. This page gives you what to log, what to alert on, how to make alerts without a Blotato webhook, a 5 line weekly check and a 4 week test. Everything is a build plan based on Blotato's documentation, checked on 21 November 2026.
Prices are in US dollars as of November 2026. Blotato's pricing page lists Starter at $29 a month, billed monthly. Its API (the way other tools talk to it) needs a paid plan, and the 7 day trial excludes it.
This page may contain affiliate links from which Blur Studio earns commissions.
What to log
Keep one row per post attempt in a sheet or table. Write the first part before you call Blotato and the rest after, so that a run that dies in the middle still leaves a trace.
| Field | Written when | Why |
|---|---|---|
| Content ID | Before | Your own key |
| Platform, account ID, destination ID | Before | Proof of where it was meant to go |
| Intended time (UTC) | Before | To spot late posts |
| Run ID | Before | Ties the row to your automation tool's run |
| Submission ID | Straight after create | Blotato's postSubmissionId. Without it you cannot look the post up. |
| Status and checked at | After each check | submitted, scheduled, published, failed, unknown |
| Public URL | On published | Proof |
| Error message | On failed | Blotato's text, unedited |
| Approved by | Before | Who said yes |
A record might look like this, as made-up JSON:
{
"contentId": "c-0231",
"platform": "linkedin",
"accountId": "ACCOUNT_ID",
"intendedTimeUtc": "2026-12-02T09:00:00Z",
"runId": "run-5521",
"submissionId": "SUBMISSION_ID_FROM_BLOTATO",
"status": "published",
"checkedAt": "2026-12-02T09:03:00Z",
"publicUrl": "https://example.com/post-url",
"errorMessage": null,
"approvedBy": "sam"
}
Blotato has three kinds of ID that must not be mixed: the submission ID returned when you create a post, the scheduled-post ID in its schedule list, and the published-post ID in its published list. Log the submission ID and look posts up with it. Blotato's own Logs page also shows each request's payload, response and error, with filters for Posts, Videos, Media, Accounts and DM and for Processing, Failed and Success. Absence from a filtered list does not prove nothing was attempted, so use your own log as the main record. See this error codes page for what the messages mean.
Alerts to set
| Alert | Trigger | How |
|---|---|---|
| A workflow crashed | Any run error | n8n error workflow, or Make error handler |
| A post failed | Blotato lists status failed | A daily check you build (no webhook) |
| A post is stuck | Log row in submitted for over 30 minutes | A check over your own log |
| Credits low | Balance below a line you choose | Daily read of the credit balance |
| Queue nearly full | Scheduled posts above 80 percent of your plan limit | Daily read of the schedule count |
| Rate limit hit | A 429 reply | Error branch in the flow |
| Nothing posted | Zero published posts in 48 hours on a daily schedule | A check over your own log |
That last one catches the silent failure. An alert that fires on the absence of a post is the safest net you can build.
There is no failure webhook, so ask on a timer
Blotato's documentation describes no webhook or callback for a post being published or failing. The documented route is to ask. Its List Posts call (GET https://backend.blotato.com/v2/posts, 60 requests a minute) returns posts in a time window with filters. The query values are since and until (ISO 8601 times, by default 7 days back and 7 days ahead), limit (1 to 250), cursor for paging, and repeatable status (scheduled, published or failed) and platform values. Each failed item carries a state with an error message. A daily watchdog flow:
- Schedule Trigger once a day (n8n's built-in timer node; n8n is a visual workflow tool).
- HTTP Request node: GET the URL above with
status=failedandsinceset to 24 hours ago, with the headerblotato-api-keykept in a credential. - IF node: continue only when the list has items.
- Send the platform, post time and error message to Slack (team chat) or email.
The same pattern works in Make with the HTTP module and in Zapier with Webhooks by Zapier. In Zapier each successful action counts as a task, so a daily check is about 30 tasks a month plus alerts, per the Zapier recipes page.
n8n and Make error handling
- n8n. Set an error workflow in Workflow Settings that starts with the Error Trigger node, and send yourself the workflow name, the failed node and the message. The Stop And Error node forces a failure when your own check says something is wrong, for example "no submission ID". Retry On Fail allows at most 5 tries and a wait of at most 5,000 ms. Do not turn it on for the publish step, since a retry after an uncertain write can post twice. Use it for status reads.
- Make. Error handlers (Rollback, Break, Resume, Commit and Ignore) and the Router cost no credits. Use Break to store a failed run for review. If Make runs out of credits, scenarios stop, so watch your credit use too. Incoming webhooks queue and polling scenarios catch up.
- Zapier. Steps that error do not count as tasks. Replaying a whole run counts the steps that already succeeded again and can double-post, so replay only the failed step after checking Blotato.
The 5 line weekly check
Do this on the same day every week, in ten minutes. Write the numbers down.
- Failed posts. List Blotato posts with status failed for the last 7 days, or open the Logs page and filter by Failed. Target: zero, or each one explained and fixed. Read the error text before you retry. An unchanged retry usually fails the same way.
- Stuck statuses. In your own log, find rows still at submitted or unknown after 30 minutes. In Blotato, in-progress is what it returns when it finds no failed, published or scheduled record, so a wrong ID also shows in-progress. Check the post by hand on the platform before you do anything.
- Credit balance. Read the balance (
GET /v2/credits, fieldcreditsRemaining, or the app). Starter includes 1,250 credits a month. Credits are spent only on AI images and video, not on publishing. Note the spend since last week. A sudden drop means a loop is generating. - Queue size. Count scheduled posts (
GET /v2/schedulesreturns a count, 50 per page). Starter holds 200, Creator 1,000, Agency 3,000. Above 80 percent, slow down what feeds the queue. A full queue rejects new posts with an error that says to remove some or upgrade. - Rate limit errors. Search your automation tool's run history for 429 replies. Blotato allows 30 create-post requests a minute, 60 status reads a minute and 30 media uploads a minute. Any 429 means too much concurrency or a loop. Lower the pace or add a wait.
Then add three quick looks that are not part of the five: does each platform's own feed match your log for the week, is the Blotato key still valid (a 401 means recopy or regenerate), and is every connected account still connected. A social account that needs to reconnect will fail posts until you fix it.
Copy this check into a sheet:
| Week of | Failed posts | Stuck rows | Credits left | Queue count of limit | 429 errors | Action taken |
|---|---|---|---|---|---|---|
Fixing what you find
| Finding | First move |
|---|---|
| Failed, error names a field | Fix the field (a Facebook post needs a Page ID, a Pinterest post a board ID), then resubmit once. |
| Failed, media error | Check the link in a private window. Temporary or login-gated links expire. Use a direct public link. |
| Failed, platform rejection | Read the platform's current rules. Do not loop retries. |
| Stuck at submitted | Look at Blotato's Posts list and the platform before any retry. |
| 401 or 403 | 401: recopy the whole key, including the trailing equals sign. A 403 reply means check billing. |
| 429 | Wait, lower concurrency, retry the read, not the publish. |
| Credits dropping | Stop the generation step and find the loop. Blotato's visual create stops with insufficient credits when the balance is short. |
| Queue full | Pause new scheduling, or move to a bigger plan. See a platform limits example. |
A kill switch is part of monitoring. Regenerating the Blotato key stops REST and automation tool calls at once, but connections made by sign-in, such as an AI assistant's connector, are not affected, so you must also disconnect those. Scheduled posts already queued will still publish unless you delete them. For duplicates and retries see the rate limits and retries guide.
The monthly review
- Count posts planned, posted and failed for the month, and compute the success rate. Blotato's analytics page also shows posts published, publishing success rate, API requests and failed posts over 7 days, 30 days or all time.
- Review which failures repeated. A repeat means a fix to the flow, not another retry.
- Check the plan still fits: accounts used out of 20, queue peak out of 200, credits used out of 1,250 on Starter.
- Rotate the API key if anyone who knew it has left.
- Read the vendors' change notes for the tools in your chain, since limits and node names change.
A 4 week test plan with pass and fail criteria
Run the log, the alerts and the weekly check for 4 weeks on a real but low-risk account, with a throwaway account for the injected failures. Never trigger a rate limit with real create-post calls: use the mock address in week 3.
| Test | Pass | Fail |
|---|---|---|
| Week 1: post with a bad media link | Row shows failed, alert arrives within a day | Row shows posted, or silence |
| Week 1: stop the workflow for 48 hours | The "nothing posted" alert fires | No alert |
| Week 2: use a wrong key in the automation | A 401 alert reaches you | Runs show success |
| Week 3: point one HTTP step at a mock address that always replies 429 (a free request-bin style service or a small local script) | A 429 is logged and the flow slows or stops | The flow keeps hammering, or a row is lost |
| Week 4: compare the log with the platform feeds | Counts match | Any post you cannot account for |
| Each week: do the 5 line check | Under 15 minutes, all five numbers recorded | You skip it |
Who should skip the full setup
Skip the alerts and keep only the weekly check if you post a few times a week. The full setup is for flows that run unattended. If your tool is a scheduler you use by hand, the app's own calendar shows you what is queued and its failed posts, which may be enough. And do not build a monitor if no one will read the alerts: an alert channel nobody watches is worse than a weekly look, because it creates false comfort.
How this page was checked
The Blotato facts come from its pricing page and help centre pages on listing posts, schedules, credits, rate limits, post lifecycle and error handling. The n8n, Make and Zapier facts come from their documentation and pricing pages. Last checked on 21 November 2026 and refreshed every 90 days. Blur Studio has not run the tool itself, so test with the 4 week plan and use Blotato's 7 day trial for the web app first.
How I'd approach this
I would do the weekly check by hand for a month before I built a single alert, because it shows me which failures actually happen. Then I would automate the one that bit me. If you are still choosing a tool, you can look at Blotato's site and its Logs and analytics pages. Week one: on day one create the log sheet, on day two add the submission ID write to your flow, on day three build the daily failed-posts check, on day four add the "nothing posted in 48 hours" alert, and on day five do your first 5 line check and write down the numbers. Keep the same day each week. If you would like a hand, the free tools at /free and the free AI brainstorm call at /ai-strategy are there.
Questions people ask
Does Blotato send a webhook when a post fails?
Its documentation describes none for post status. Ask on a timer with List Posts filtered to failed, or check a single post by its submission ID. See the approval step guide for a related build.
How often should I check an automation?
A 10 minute check once a week, plus an automatic daily alert for failures and for "nothing posted in 48 hours". Check more often for the first 2 weeks after a change.
What should I log for each post?
Your content ID, platform and account, intended time, run ID, Blotato's submission ID, status, public URL, error message and who approved it. Write the first fields before you call Blotato.
What does in-progress mean in Blotato?
It is what Blotato returns when it finds no failed, published or scheduled record. A wrong ID also returns it, so a post stuck at in-progress needs a manual look at the platform and your log.
How big is the Blotato queue?
As of November 2026, Starter holds 200 queued scheduled posts, Creator 1,000 and Agency 3,000. Posts published immediately do not count.
What rate limits should I watch for?
Blotato lists 30 create-post requests a minute, 60 status reads a minute and 30 media uploads from a link a minute. A 429 reply means you went over. Read the n8n node guide for the check step.
Should I turn on automatic retries?
For reads, yes with a cap. For publish steps, no. Blotato has no idempotency key, so a retry after an uncertain write can post twice. Look at the Posts list first.
More in this topic: Social media: automation with n8n, Make and Zapier (27 guides) →