Integrations, one pair at a time
Each page pairs two connectors with a worked flow, a starting field map, what syncs in each direction, and how approvals and audit apply. Facts about each connector come from the platform as it ships, not from a brochure.
How to read these pages
A pairwise page is a starting point, not a template you are locked into. The worked example is one flow teams actually build first, the field mapping is the map that flow starts from, and the direction table says what moves each way. Where a connector publishes typed output schemas, the mapping can be verified against them in the builder. Where it does not yet, the page says so and the mapping is configured in the flow.
Every pair runs on the same platform as every other flow: the same connectors, the same run history with step-level detail, the same approvals when a person needs to decide, and the same tamper-evident audit log for every action.
Not seeing your pair?
Any two of the 239 connectors can be combined in a flow, and a Poll for changes trigger or an inbound webhook endpoint gives any pair an event-driven start. If the pair you need is not documented yet, bring it to a demo and we will build it against your own systems.
Frequently asked questions
Do these pages describe pre-built templates?
They describe flows built from standard steps on the platform: a trigger, a lookup, a mapping, a write, and the approvals and error handling around them. Nothing on these pages needs code, and every step is visible in the run history when it runs.
How current are the connector facts?
The operation counts, trigger counts, and delivery kinds on each page are generated from the connector catalog as the platform ships, and they update whenever the catalog does.
Bring one real integration
We will build it with you against your own systems, with the run log open.