Zapier, Make and n8n

Run a workflow when a post changes

Create a webhook trigger in your tool (a Zapier Catch Hook, a Make Custom webhook, or an n8n Webhook node) and copy its URL. Then subscribe that URL to CMSKite in one of two ways.

• In the dashboard: open Developers → Webhooks and add the URL. See Webhooks.
• With the API: call the subscribe endpoint below. This is what a tool uses when it sets up its own trigger.

The events are post.published, post.updated, post.unpublished and post.deleted. Each delivery is signed like any other webhook. Check the signature as described in Webhooks.

Subscribe and unsubscribe

Send url, events (at least one) and an optional description of up to 200 characters. The answer is 201 with the id, url, events, secret and createdAt. Keep the secret to verify deliveries.

curl -X POST https://cmskite.com/v1/hooks \
  -H "Authorization: Bearer csk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"url":"https://hooks.zapier.com/hooks/catch/123/abc","events":["post.published"]}'

What the trigger receives

The delivery holds the event name, the time and the post's id, slug and status. It does not hold the post text. Add a step that reads the post with GET /v1/blog/posts/{id}.

{
  "id": "evt_...",
  "event": "post.published",
  "occurredAt": "2026-10-28T09:00:00.000Z",
  "projectId": "...",
  "data": { "id": "...", "slug": "my-post", "status": "published" }
}

Read and write posts

• Read posts: add an HTTP or Webhooks step that calls GET /v1/blog/posts with your API key. See Authentication.
• Write posts: an AI assistant over MCP is the simplest way today.