Voyager's beta integration set spans productivity, communications, CRM, work management, files, automation, calling, meetings, payments and open calendar/contact standards. Gmail is the one deliberately limited connection while Google certification completes, and a much larger connector set is already in development.
These connection paths are part of the beta integration set. Exact read, write, sync and action scope depends on provider authorization and Voyager configuration.
Gmail works with a deliberately limited beta scope while the Google certification process is completed. The limitation is provider-certification related rather than a separate Voyager product tier.
These connectors are being completed and activated for the beta period. They should not be represented as generally open until their activation path is live.
These are active connector targets already in development. The grouped reference below shows the same pipeline by category.
The useful question is not whether Voyager can display another provider logo. It is whether a signal in that provider can participate in a real operating loop: a customer reply changes work, a CRM update affects follow-up, a file change needs approval, or a project-system change affects a commitment elsewhere.
Voyager can begin across the existing stack and let consolidation happen later, only where native capability makes another workflow genuinely redundant.
Connect supported Microsoft 365 context to Voyager so email, calendar and collaboration changes can inform the customer, work and follow-up they affect.
Connect supported Slack conversation signals to Voyager so important channel or message activity can participate in wider work, request and decision context.
Connect supported HubSpot CRM context to Voyager so customer and opportunity changes can inform communications, work, schedules, approvals and downstream follow-up.
Connect Pipedrive organizations, people and deals to Voyager so commercial context can stay attached to relationship activity, delivery and follow-up.
Connect supported Asana work context to Voyager so project changes can inform customers, communications, schedules, approvals and other responsibilities outside the project system.
Connect supported ClickUp work context to Voyager so changes in the workspace can participate in wider customer, communication, scheduling and approval workflows.
Connect supported Dropbox file and folder context to Voyager so document changes can inform customers, work, requests, decisions and follow-up.
Connect supported Voyager events and actions to Zapier so existing cross-app automation can participate in Voyager workflows without becoming Voyager's internal authority model.
Connect supported Voyager events and actions to Make scenarios through the governed automation adapter without handing Make Voyager's internal data or authority model.
These are active development targets, not a generic backlog. They are shown as in development until the connector and activation path are ready for users.
Intercom · Freshdesk · Zendesk · Drift
Fireflies · Canva · Notion · Trello · Loom · Deel
Claude · Gemini · Vertex AI · SciSpace · Midpage · Consensus · Scite
Shopify · Etsy · Wix · Squarespace · WooCommerce
Skyscanner · Trip.com
Outscraper · Apollo · Google Places · Gravatar
Google Analytics · Microsoft analytics · Meta analytics · Facebook & Instagram messaging
Apple Reminders · HealthKit
Alpaca
The development set spans service desks, work and content, AI/model providers, research systems, commerce, travel, enrichment, analytics, messaging, personal/health and specialty data. Those connections extend the same context → intelligence → governed action loop rather than creating separate product silos.
Provider names on this page indicate connection status only. They do not imply endorsement, certification or a partnership unless separately stated.
Estimate how much coordination time, follow-up drag and tool sprawl Voyager can remove from your week, without forcing a rip-and-replace rollout.
fewer manual follow-ups
tools partially consolidated
faster response coordination
commitments captured automatically
Fast wins. Real momentum.
Connect what matters most.
Directional modeled estimate based on the selections above. Actual impact varies by workflow design, adoption, connected systems and the authority you give Voyager.
Tell us which systems your first beta workflow depends on. We will use the smallest useful connection set rather than make migration the first project.
Request early access
