Contact Book a call

Integrations

Connect the tools your business runs on.

Two-way syncs that stay right after the first week: upserts keyed on the record, retries, reconciliation and an alert when something goes quiet. Every account in your name.

10 integrations

Tools, A to Z

55 tools we build on and connect.

Every tool has its own page: what we build on it, what we sync, and which tools it usually needs to talk to. Not listed? Anything with an API or a database we can read works the same way.

In every build

Not a Zap. A system with a runbook.

Under the hood

  • Upserts keyed on the record

    Every write is matched on the source ID. A retry or a re-fire updates the existing record instead of creating a second one.

  • Retries with backoff

    Rate limits and timeouts are retried with increasing delays, then parked for review, never dropped.

  • Idempotent, loop-safe writes

    Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.

  • Reconciliation

    A nightly job compares counts and totals on both sides and lists any record that differs.

  • Audit log

    Every run records input, mapping result, action taken and who or what triggered it. Searchable by record.

For the team

  • Slack or email notifications

    The alerts go to a named person, not a channel nobody reads. You choose Slack, email, WhatsApp or all three.

  • A runbook

    One document per integration: what it does, what each alert means, and what to do in the first ten minutes.

  • Training

    A live session with the people who will use the review queue, recorded for whoever joins later.

  • Handover

    Admin access, billing and code sit in accounts in your name from day one. If we leave, it keeps running.

  • Sixty days of hypercare

    The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.

Need a pair that is not listed?

Anything with an API.

These are the integrations we are asked for most. The approach is the same for any tool with an API or a database we can read. Tell us what you are trying to connect and we will say whether it needs a build or an off-the-shelf tool will do.

See how we work
A team of six gathered around one screen in an open-plan office
Thirty minutes with the people who own the process. Photo: Vitaly Gariev, Unsplash.