Use Wavefront with Zapier, Make and n8n

Zapier, Make and n8n connect Wavefront to tools it has no direct destination for, such as Airtable, Google Docs or a project tracker. Wavefront’s event webhooks start a workflow, and a workspace API key lets the workflow act in Wavefront: start drafts, publish approved work or export an article.

Wavefront apps for Zapier and Make are not in their public directories yet. Until they are, connect either platform with its own webhook trigger and HTTP request steps. n8n works the same way with its Webhook, Code and HTTP Request nodes.

What you need

1. A Wavefront owner to create an API key under Settings → API and MCP. See API keys and webhooks.
2. The right scopes for what the workflow does:

To use	Scopes
Any trigger	webhooks and generations:read
Start a draft, draft a calendar post, message the strategist	generations:write
Publish an approved version	publish
Add a workspace document	context:write
Export a version	generations:read (a draft that isn’t approved also needs generations:write)

3. The trial or the plan on the workspace.

Triggers you can use

Trigger	Event
Draft ready for review	A draft or revision finished
Version approved	A person approved a version. Carries the version id for publishing or exporting
Published	A post went live. Carries its URL
Draft needs input	A draft is waiting for answers
New comment	Someone commented. Carries an excerpt
Plan saved	A strategy’s plan was saved
Suggestions ready	New suggestions from search data are waiting

Actions you can take

• Start a draft.
• Draft a calendar post.
• Message the strategist.
• Add a workspace document.
• Publish an approved version.
• Export a version as JSON, Markdown or HTML.

Drafting and the strategist’s reply take time. The action returns at once, and a later trigger, such as Draft ready for review or Plan saved, picks up the result.

Set up a workflow

1. In your platform, add a webhook trigger and copy its public address.
2. Subscribe that address to the events you want with your API key. The subscription returns a signing secret once; store it in the platform.
3. Verify each delivery’s signature with that secret before the rest of the workflow runs.
4. Add HTTP request steps for the actions, sending the key as a bearer token. Turn on retries for rate limits and server errors.

The integrations guide has the exact requests and an n8n Code node that verifies signatures. The webhooks guide has samples in other languages.

Subscriptions your platform creates show in Settings → Integrations → Event webhooks, where an owner can pause or delete them.

Example workflows

• Approved article to Notion, Airtable or Google Docs. Trigger on Version approved, continue only for articles, export the version as JSON, then create the page, record or document from its fields.
• Published article to a newsletter tool. Trigger on Published, export the version, then create a campaign draft with the title, description and link.
• New calendar posts to Asana or another tracker. Trigger on Plan saved, list the strategy’s calendar, skip posts you’ve seen, and create a task for each new one.

Wavefront also connects directly to Asana and Trello for project tasks, and to Slack and Microsoft Teams for messages, under Settings → Integrations.

Or publish through a webhook destination

To send each published article to a workflow, you can add a webhook destination under Settings → Publishing instead. Every publish then sends the full article to the platform’s address, and withdrawing sends a delete event. Zapier, Make and n8n don’t check signatures on their incoming webhooks, so treat the address as a secret.

What automations can’t do

Approval is never available to a key. A person approves in the web app, and Version approved fires then. Keys also can’t post to social networks or send newsletters.

If something goes wrong

• Deliveries arrive twice. Delivery is at least once. Skip duplicates using the event id in the webhook-id header.
• The signature check fails. Verify against the raw body, before any parsing, and check you stored the latest secret.
• The webhook turned off. Deliveries failed for 24 hours, or your endpoint answered 410. Fix it, then turn it on again in Settings.