INTEGRATION · MAKE

Extend Voyager with Make scenarios, through a governed gateway.

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

What the current implementation supports.

Workflows it supports. Use a Make scenario to react to Voyager task/workstream changes or create Voyager work from an external scenario.

Connected systemMake

The adapter uses installation-bearer authorization and only the events/actions declared by the Automation Gateway descriptor.

VoyagerBusiness context

Make can invoke the supported Automation Gateway actions; Voyager can emit task.created, task.updated, workstream.created and workstream.updated trigger events.

Where authorizedGoverned action

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

Four Voyager events are exposed today.

The current adapter exposes task.created, task.updated, workstream.created and workstream.updated through REST-hook triggers.

02ACTIONS

Two Voyager create actions are exposed today.

The current action contract allows Make to create a Voyager task or a Voyager workstream.

03BOUNDARY

The adapter is a defined interface, not open access.

Installation-bearer authorization and the adapter descriptor limit scenarios to the declared triggers and actions.

CONNECTION QUESTIONS

What to know before you connect.

Can a Make scenario connect to Voyager?
Yes, when it uses the currently exposed task/workstream triggers or create actions.
Can Make invoke any Voyager action?
No. The current adapter exposes only task.create and workstream.create.
Does Voyager depend on Make?
No. Voyager's native automation runs independently.

Get started

Bring one Make scenario that should exchange work with Voyager.

We will map it to the supported task/workstream trigger and create-action contract.