Integrations · 142 native connectors · 4 added in march

Speaks to everything you already run.

Postgres to Snowflake, Stripe to NetSuite, Salesforce to that one internal API nobody touches. All live, all monitored, all part of the same workflow graph.

142Native connectors

All built + maintained in-house.

18In beta

Join the early-access list in docs.

<48hAvg bug fix SLA

When a vendor breaks their API, we fix it.

SDKBuild your own

TypeScript + Python. 80 lines for a basic connector.

⌘K
All · 142 Databases · 18 Payments · 14 CRM · 11 Data warehouse · 8 Messaging · 16 Analytics · 12 Files · 9

Most popular · used by 60%+ of customers

Databases · 18 connectors

VIEW ALL →

Data warehouse & Analytics · 20 connectors

VIEW ALL →

Payments & Billing · 14 connectors

VIEW ALL →

CRM, Support & Messaging · 27 connectors

VIEW ALL →

Don't see it? Build it in an afternoon.

The Conduyt Connector SDK is TypeScript or Python. A working custom connector is about 80 lines. Publish it private to your team, or submit it for review and we'll ship it in the official registry.

acme-connector.ts
import { defineConnector } from '@conduyt/sdk'; export default defineConnector({ name: 'acme', auth: { type: 'oauth2', scopes: ['read'] }, // three actions, three triggers — that's it actions: { createInvoice: { ... }, syncCustomer: { ... }, }, triggers: { invoicePaid: { webhook: '/hooks/paid' }, }, });

How to read this directory

Integrations get listed here only once they work. Anything still being built stays off the page, because a directory that lists intentions is a directory you cannot trust. Each entry falls into one of two tiers, and the tier tells you more about the integration than the logo does.

Platform-native

Built into Conduyt and always on. There is no account to create on the other side, no API key to store or rotate, and no second subscription. The capability is part of the $299 per month plan.

The Resend email delivery layer is the example: sending simply works, and the only setup is authenticating your own domain.

Connected app

You bring your own account with the other vendor and connect it. Your contract, your data and your bill stay with them, which is what keeps things like phone numbers portable.

Twilio, Warmy, Hyros and Zapier all work this way. Usage on their side is billed by them, not by Conduyt.

What to check before you connect anything

Every integration page here publishes the same five things: what the integration does, what you need in place before you start, what data moves and in which direction, what it does not do, and the specifications. Read them in this order.

  1. Who bills you. Platform-native costs nothing extra. A connected app means a second invoice, and that belongs in the evaluation rather than in the surprise column.
  2. Which direction data moves. Reading data out is a very different risk from letting a third party write into your pipeline. The data flow table on each page states it row by row.
  3. What has to exist first. Some prerequisites are slow. US SMS registration and email domain warmup both take longer than the software setup does, so they belong at the start of the plan rather than the end.
  4. What it does not do. Each page carries a limits section, and it is the section worth reading first. It is faster to rule an integration out in two minutes than to discover the gap after migration.
  5. Whether the API would be simpler. With 610+ REST API endpoints and 880+ API operations, a direct build is sometimes cleaner than a connector. The MCP server exposes 170+ tools for the same reason on the agent side.

Connect everything. Break nothing.

Build reliable integrations with our Idempotency Checklist for Webhooks.

Try every integration free for 20 days. Unlimited users, unlimited connectors, no credit card.