What it does
n8n works with Wavefront through its built-in Webhook, HTTP Request and Code nodes, on n8n Cloud or a self-hosted instance with a public https address.
A Webhook node receives Wavefront's signed events, a Code node checks the signature, and HTTP Request nodes call the REST API to start drafts, publish approved versions and export articles.
Before you start
- n8n Cloud, or self-hosted n8n behind a public https host
- A workspace API key, created by an owner
How to connect n8n
- In Wavefront, an owner opens Settings → API and MCP and creates a key with the scopes the workflow needs.
- In n8n, create a Header Auth credential named Authorization with the value Bearer and your key.
- Add a Webhook node with Raw Body on, activate the workflow and copy its production URL.
- Subscribe that URL to the events you want with one call to Wavefront's webhooks endpoint, and store the signing secret it returns.
- Add the Code node from the n8n guide to check each delivery's signature, then HTTP Request nodes for actions.
What it covers
- Every public event, such as version approved, published, needs input, comment and plan saved
- Signed deliveries, with a ready-made Code node that checks them
- Every REST action: start a generation, draft calendar posts, message the strategist, add a document, publish, export
Good to know
- There is no Wavefront node. You build with n8n's general nodes.
- n8n doesn't subscribe on its own; you make and delete the subscription yourself.
- Self-hosted instances must allow the crypto module for the signature check.