Integrations · 200+ first-party

Wherever your team works — Routix is already there.

Not just OAuth. Semantically correct, bidirectional, idempotent. Every integration ships with golden-set evals so your agents don't break when the upstream API does.

CRMSalesforceBi-directional · idempotent
CRMHubSpotNative API
CRMPipedriveNative API
SupportZendeskTriage + draft
SupportIntercomInbox + Fin
SupportFrontThreads + drafts
CommsSlackApp + bot · DMs
CommsMicrosoft TeamsBot + adaptive cards
CommsGmailRead · draft · send
CommsOutlook 365Read · draft · send
PMLinearEvents + actions
PMJiraCloud + Data Center
PMAsanaTasks + projects
PMNotionRead + write
ERPNetSuiteSuiteTalk · RESTlets
ERPSAP S/4OData + IDoc
ERPOracle FusionREST
FinanceStripeBilling + Connect
FinanceQuickBooksOnline + Desktop
FinanceRampCards + spend
HRISWorkdaySCIM · RaaS
HRISRipplingNative
HRISBambooHRNative
DataSnowflakeRead · materialize
DataBigQueryRead · stream
DataDatabricksSQL + Unity
StorageGoogle DriveDoc ingestion
StorageDropboxDoc ingestion
StorageBoxDoc ingestion · ACL-aware
StorageAmazon S3Object store
DevGitHubPRs · checks · issues
DevGitLabPipelines + MRs
DevSentryIssues + alerts
IdentityOktaSCIM · SSO
IdentityAzure ADSCIM · SSO
IdentityGoogle WorkspaceSCIM · SSO

Need something not listed? Request an integration → or build your own with the Routix MCP SDK →.

What "deep integration" actually means.

01

Bi-directional

Read state, write state, react to events. Not read-only or fire-and-forget — full participation.

02

Idempotent

Re-runs are safe. Routix never double-charges, double-creates, or double-notifies.

03

ACL-aware

Permission checks at query time. Agents see only what the requesting user can see.

04

Semantically correct

Field mappings hand-curated by a Routix engineer per system. No "best-effort" guesses.

05

Versioned

Upstream API change? Routix pins, tests, and migrates. Your agents don't notice.

06

Evaluated

Every connector ships with a golden-set test suite. Drift triggers an internal block.