01WHAT IT CONNECTS
Task and project changes from ClickUp.
Supported ClickUp work informs Voyager, so changes reach customer updates, approvals and schedules without manual status-chasing.
INTEGRATION · CLICKUP
Voyager's ClickUp connector implements OAuth, workspace selection, user binding, synchronization, webhook handling and outbound push for Voyager workstreams and tasks. It is designed for coexistence rather than universal ClickUp object parity.
The connection at a glance
Workflows it supports. Keep delivery work in ClickUp while customer, approval and schedule consequences are coordinated in Voyager.
OAuth authorization, workspace selection, user bindings and Voyager integration permissions define the boundary.
Selected ClickUp workspace and supported work-item context through synchronization and webhook handling.
Voyager can push mapped workstreams and tasks into ClickUp.
Voyager's own equivalentVoyager Work, Vault, Discuss, Relations and finance capabilities can run the surrounding work natively.
Keep it, replace it, or bothKeep ClickUp for teams that need it, or move selected work into Voyager where cross-functional context matters more.
01WHAT IT CONNECTS
Supported ClickUp work informs Voyager, so changes reach customer updates, approvals and schedules without manual status-chasing.
02NATIVE ALTERNATIVE
Voyager covers projects, tasks, documents, discussion and meetings natively, and adds CRM, service, finance and operations, all connected through one operating context.
03YOUR CHOICE
Keep ClickUp where teams are well established, and move work into Voyager where it is most connected to customers and money.
CONNECTION QUESTIONS
Get started
We will map the selected workspace, supported work sync and any Voyager work that should be pushed back.