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 · MAKE
Voyager's Make adapter uses the same bounded Automation Gateway contract as Zapier. It currently exposes task/workstream creation and update triggers, plus actions to create a Voyager task or workstream. Other Voyager events and actions are not implied.
The connection at a glance
Workflows it supports. Use a Make scenario to react to Voyager task/workstream changes or create Voyager work from an external scenario.
The adapter uses installation-bearer authorization and only the events/actions declared by the Automation Gateway descriptor.
Make can invoke the supported Automation Gateway actions; Voyager can emit task.created, task.updated, workstream.created and workstream.updated trigger events.
The current Make action contract exposes task.create and workstream.create.
Voyager's own equivalentVoyager automation, approvals and Workers handle native workflows inside Voyager.
Keep it, replace it, or bothKeep Make for external app reach and use Voyager-native automation for workflows already inside the platform.
01TRIGGERS
The current adapter exposes task.created, task.updated, workstream.created and workstream.updated through REST-hook triggers.
02ACTIONS
The current action contract allows Make to create a Voyager task or a Voyager workstream.
03BOUNDARY
Installation-bearer authorization and the adapter descriptor limit scenarios to the declared triggers and actions.
CONNECTION QUESTIONS
Get started
We will map it to the supported task/workstream trigger and create-action contract.