What it does
Connect Wavefront to the tools it has no direct connection for. Zaps can start when a draft is ready for review, a version is approved, a page goes live, a comment is posted or a plan is saved.
Actions start drafts, draft calendar posts, message the strategist, add workspace documents, publish approved versions and export articles. There's no approve action, so approving happens in Wavefront.
Before you start
- A Zapier account
- A workspace API key with the scopes your Zaps need, created by an owner
How to connect Zapier
- In Wavefront, an owner opens Settings → API and MCP and creates a key with the webhooks and generations:read scopes, plus any action scopes.
- In Zapier, add the Wavefront app and paste the key.
- Pick a trigger, such as Version Approved, and test it with sample data.
- Add actions, such as Export a Version or Publish an Approved Version, then turn the Zap on.
What it covers
- Instant triggers: Draft Ready for Review, Version Approved, Published, Draft Needs Input, New Comment, Plan Saved
- New Calendar Post, checked on a schedule
- Actions: Start a Generation, Draft a Calendar Post, Message the Strategist, Add a Workspace Document, Publish an Approved Version, Export a Version
- Every delivery is signed and checked
Good to know
- There is no approve action.
- Until the Wavefront app is in Zapier's public directory, a webhook destination or an event webhook can send Wavefront's events to a Webhooks by Zapier catch hook.
- Export offers JSON, Markdown and HTML; the zip isn't offered.
- A workspace has at most 20 webhook subscriptions, and each Zap with a Wavefront trigger uses one while it is on.