01TRIGGERS
Four Voyager events are exposed today.
The current adapter exposes task.created, task.updated, workstream.created and workstream.updated through REST-hook triggers.
INTEGRATION · ZAPIER
Extend Voyager to more apps with Zapier, through a governed gateway.
Voyager's Zapier adapter is implemented, but its current contract is deliberately narrow. It exposes four REST-hook triggers for task and workstream creation/updates and two actions that create a task or workstream. It is not unrestricted access to every Voyager object.
The connection at a glance
What the current implementation supports.
Workflows it supports. Use a Zap when another app should react to Voyager task/workstream changes or create a Voyager task/workstream from an external workflow.
The adapter uses installation-bearer authorization and only the events/actions declared by the Automation Gateway descriptor.
Business contextZapier can invoke the supported Automation Gateway actions; Voyager can emit task.created, task.updated, workstream.created and workstream.updated trigger events.
The current Zapier action contract exposes task.create and workstream.create.
Voyager's own equivalentVoyager automation, approvals and Workers handle native workflows inside Voyager without Zapier.
Keep it, replace it, or bothKeep Zapier for external app reach. Use Voyager-native automation where the systems and records already live inside Voyager.
02ACTIONS
Two Voyager create actions are exposed today.
The current action contract allows Zapier to create a Voyager task or a Voyager workstream.
03BOUNDARY
The gateway is intentionally narrower than Voyager's internal API.
Installation-bearer authorization and the adapter descriptor limit external automation to the declared triggers and actions.
CONNECTION QUESTIONS
What to know before you connect.
- Can an existing Zap connect to Voyager?
- Yes, when it can use the currently exposed task/workstream triggers or create actions.
- Can Zapier invoke any Voyager action?
- No. The current adapter exposes only task.create and workstream.create.
- Does Voyager depend on Zapier for automation?
- No. Voyager's native automation runs independently.
Get started
Bring one existing Zap that should exchange work with Voyager.
We will map it to the currently supported task/workstream triggers or create actions instead of assuming arbitrary API access.