How do I connect Zapier or n8n to VeloCMS?

VeloCMS connects to Zapier, n8n, Make (formerly Integromat), and any other automation platform that accepts outbound webhooks. Go to Admin → Settings → Integrations → Webhooks, add a new endpoint URL (your Zapier webhook URL or n8n webhook trigger URL), choose which events you want to trigger it, and click Save. VeloCMS will send an HTTP POST with a JSON payload to that URL every time the selected event fires.

Which events can trigger a webhook?

VeloCMS currently fires webhooks on four events: post.published (fires when a post is published or a scheduled post goes live — payload includes the post title, slug, URL, excerpt, author, and publish timestamp), subscriber.created (fires when a reader creates a free or paid account — payload includes the email, plan, and timestamp), subscriber.cancelled (fires when a paid subscriber cancels — payload includes email, plan, and cancellation reason), and order.completed (fires when a commerce order is fulfilled — payload includes order ID, total, and line items). The post.published event is the most commonly used trigger for social media automation.

How do I set up a Zapier zap for new posts?

In Zapier, create a new zap and choose Webhooks by Zapier as the trigger. Select Catch Hook as the event. Zapier gives you a unique webhook URL — copy that URL. In VeloCMS, go to Admin → Settings → Integrations → Webhooks, paste the URL, check the post.published event, and save. Back in Zapier, click Test Trigger — you'll need to publish a test post in VeloCMS (or use the Send Test Event button in VeloCMS's webhook settings) so Zapier can see the payload structure. Once Zapier captures the test event, you can build actions like posting to a Slack channel, adding a row to a Google Sheet, or sharing on X/Twitter.

How do I set up an n8n workflow for VeloCMS?

In n8n, add a Webhook trigger node and copy the production webhook URL. Paste that URL into VeloCMS's webhook settings exactly as you would for Zapier. The n8n workflow receives the same JSON payload as Zapier. n8n is a particularly good match for VeloCMS power users because it's self-hostable (no per-task pricing), supports JavaScript functions inside workflows, and has native HTTP nodes that can call the VeloCMS REST API to pull additional post data beyond what the webhook payload includes.

Are webhook deliveries reliable and do they retry on failure?

VeloCMS delivers webhooks with at-least-once semantics — if the receiving server returns a non-2xx HTTP status or doesn't respond within 10 seconds, VeloCMS retries the delivery three more times with exponential backoff (5 seconds, 25 seconds, 125 seconds). After four failed attempts the delivery is marked as failed and logged in Admin → Settings → Integrations → Webhook delivery log. The log shows each delivery attempt's timestamp, HTTP status, and response body so you can diagnose failures. If your automation platform goes down for maintenance, you can replay failed deliveries manually from the log.