Webhook
Connect Webhook to Citeca and publish articles automatically.
Have every new article POSTed to your own endpoint as it publishes, and do whatever you like with it.
Setup time
About 2 minutes
Access needed
Admin on the site or store
What we touch
Blog posts only
Note
This connection can only read and publish blog posts. Your theme, products and settings are never modified.
What you need#
- An HTTPS endpoint that accepts POST requests
- Optionally, a bearer token so you can verify the request came from us
Connecting Webhook#
Open Settings → Publishing, find Webhook and press Connect. The wizard walks you through the steps below.
- 1
Add your webhook
We’ll POST the article payload (title, HTML, meta) to your URL on publish.
- Webhook URL
- Bearer token — At least 8 characters. Check it on your endpoint so only Citeca can post to it.
Webhook connected
We’ll POST every new article to your endpoint as it’s published.
Check it worked#
Verify it’s working
3 checks
- A test publish reaches your endpoint.
- The bearer token arrives in the
Authorizationheader, if you set one. - Your endpoint answers
2xxand the editor shows the destination as delivered.
To test without waiting for a scheduled article, open any finished article in Blog content and press Publish. You get a result per destination immediately, including the exact error if something is wrong.
Managing the connection#
Once connected, the Webhook card shows a green Connected dot and a Manage button. Everything about the connection is changed from there — there are three controls.
- Test connection — checks the credentials against Webhook right now. If they fail you get the platform’s own response, not a generic message.
- Reconnect — walks through the setup again. This is how you paste a rotated credential or change where we publish. It replaces what is stored rather than adding a second connection.
- Disconnect — deletes the stored credentials and stops publishing. Articles already published stay on your site untouched, and your drafts and schedule in Citeca are kept.
Note
When something fails you get a plain explanation and the steps to fix it. The platform’s own response — status code, endpoint and response body — is folded away under Details for support; “Copy error report” puts all of it in one paste for a support message.
TroubleshootingQuestions#
Does republishing send the article again?
Yes. Every publish and republish POSTs, with the same slug each time. Match on the slug in your handler and update rather than insert, or you will accumulate copies — we cannot dedupe inside your system for you.
What if my endpoint is down?
A non-2xx reply or a timeout is recorded as a failed publish, with the status you returned shown in the editor, and retried a few times. Other destinations are unaffected.
I changed the bearer token on my side.
Press Manage → Reconnect and set the new one, otherwise your endpoint rejects our requests and every publish is recorded as failed.
POST /your-endpoint
Content-Type: application/json
Authorization: Bearer <your token, if set>
{
"title": "How to choose a CRM for field teams",
"slug": "how-to-choose-a-crm-for-field-teams",
"html": "<h1>…</h1>",
"metaDescription": "…",
"heroImageUrl": "https://…",
"publishedAt": "2026-09-18T10:00:00.000Z"
}Note
Answer with a 2xx status. A non-2xx reply is treated as a failed publish, reported in the editor with the status you returned, and retried.
Something missing or wrong here? Tell us and we will fix it.