We don't have a page of logos to show you. What we're building instead is a real REST API and outbound webhooks, so your list is never trapped — and every integration after the first is a listing, not a six-month build.
Rather than hand-build a handful of one-off integrations, we're designing one versioned API (/v1) that the dashboard itself will run on. The two most-asked-for consumers of it, below, are the first things it's designed for.
Key-authenticated, versioned at /v1, built to the conventions integrators already expect (cursor pagination, idempotent writes, RFC 9457 errors) rather than something we invent.
Real-time events out of Peak Campaign, so your own tools hear about a change the moment it happens instead of polling for it.
Every established sender advertises a big number here — 250, 700, 1,000. We'd rather show you the honest number and tell you what it takes to change it, than pad the page with logos of tools we've never actually tested.
Once the API and webhooks ship, a Zapier, Make, or n8n listing is packaging on top of a contract that already works — not a separate integration built and maintained from scratch. That's why the API comes first: it turns every integration after the first into a much smaller job.
Tell us what you're trying to connect and we'll factor it into what we build first. This goes to a real inbox we read — not a form that disappears into a ticket queue nobody looks at.
Get early access and we'll let you know the moment keys and webhooks are ready to use — before the public announcement.