Adding real-time subscribe for a new provider now takes days | Ampersand Changelog

Adding real-time subscribe for a new provider now takes days

Enterprise B2B SaaS and agentic products not only want to read and write data into their customer’s system of record, but they want to know when specific changes happened. In our most advanced deep connectors, Ampersand supports listening to these changes through our subscribe actions.

Adding real-time subscribe support to a provider previously meant work in our open-source connectors library and additional Ampersand platform work before we could fully deploy. Now subscribe actions can be added directly to our public repo without the need for platform work.

Supporting a subscribe action for a new provider in Ampersand includes:

  1. Understanding the provider: how it signs its webhooks, what its events look like
  2. Registering and configuring the subscription: how to register the event, how to configure the subscribe action (moved to the connectors library)
  3. Running each event: routing it to the right installation, fetching the full record and mapping it to the correct fields, delivering it to the destination
Before
Connectors library
webhook signing event shapes
Ampersand platform
registration subscribe config routing delivery
A pull request in each repository. Reviewed by different people on different cycles.
After
Connectors library
webhook signing event shapes registration subscribe config
Ampersand platform
routing delivery
Connector subscribe logic fully lives in one public repository.

Platform work unblocks open-source builders

Take every provider that gained real-time this summer and count how much work was required by a platform engineer.

Provider Added Platform PRs
Jobber7 Jul
Attio21 Jul
Google Calendar27 Jul
7 Aug the per-provider subscribe logic fully moves into the connectors library
Stripe12 Aug none
Zoho Mail14 Aug none

Subscribe connector work no longer requires separate engineers to build in the Ampersand platform, which increases our open-source contributor velocity.

The path is seven documented pull requests in the connectors library, and the provider stays switched off until the last one merges.

Available now

The connectors library is public and MIT licensed, so the work behind every real-time provider is readable, including the guides describing how each one was added.

A new take on native product integrations