Webhooks (n8n and your own server)
Signed JSON to your URL when a post is approved, published or fails, or when a new idea or feedback comes in.
Updated:
A webhook sends a JSON message to the HTTPS address you choose on every selected event – so Sayweek events can flow into n8n, your own server, a spreadsheet or a CRM.
Events
- post approved · post published · publishing failed
- client feedback · new comment
- new idea · draft ready for approval
Set up
- Open Settings → All integrations and click the Webhooks · n8n card (owner permission needed).
- Enter the receiving URL (only addresses starting with
https://are accepted). - Turn off the events you don't need – all are selected by default.
- Click Add.
- Copy the Signing secret with Copy – you only see it now.
What you receive
A POST request with { event, data, at }, an X-Sayweek-Event header (the event name, e.g. post.published) and an X-Sayweek-Signature: sha256=<…> header. The signature is the HMAC-SHA256 of the request body with the signing secret – compute it on your side too and only accept requests whose signature matches.
The card shows the last HTTP status and time for each webhook (nothing sent yet until the first event). Test connection only reads and sends no message.
Disconnect
- Open the Webhooks · n8n card.
- Click Delete in the webhook's row.
Was this article helpful?
Related articles
- ZapierThe Sayweek app for Zapier: triggers for new ideas, drafts, approvals and published posts, actions for ideas, drafts and news sources.
- Make (Integromat)The Sayweek app for Make: instant triggers and modules for ideas, posts and news sources – connected with an API key.
- REST API: API keys and scopesCreate an API key, understand the read / write / approve scopes, the main endpoints and how to revoke a key.
- Developer tools: API, webhooks, MCPWhat Sayweek offers developers and automation: REST API, signed webhooks, Zapier, Make, Claude and ChatGPT (MCP) and an iCal link.