Integrations
Built-in providers for Stripe, Shopify, Microsoft 365, DocuSign and ten more give your workflows typed actions and the events that start them. Where no provider exists, the HTTP step calls the system's API directly, or your team registers a custom integration once for every workflow to reuse.
30-day trial with Pro capabilities · no card required
The connection catalog
Built-in actions take named inputs, and 518 of the 539 declare the output fields the next step reads. Provider events start runs with the event's data attached. Systems without a built-in provider get two more paths: the HTTP step and a custom integration your team defines once.
Stripe
Payments and billing
93 actions59 events
Google Workspace
Gmail, Calendar, Drive, Sheets, Contacts, Tasks
60 actions18 events
Shopify
Commerce
52 actions
UPS
Shipping and tracking
51 actions6 events
PayPal
Payments
49 actions45 events
Microsoft 365
Mail, Calendar, Teams, OneDrive, SharePoint, Excel
36 actions6 events
monday.com
Work management
33 actions21 events
Slack
Messaging
31 actions
Apollo.io
Sales data
30 actions
SendGrid
Email delivery
25 actions
Twilio
SMS and voice
21 actions
WhatsApp Business
Messaging
21 actions8 events
DocuSign
E-signature
19 actions11 events
Dropbox
Files
18 actions3 events
Typed action Stripe
Create invoice
Inputs
Outputs
No built-in provider?
HTTP step
Call any internet-reachable endpoint with basic, header, bearer, API-key or custom authentication.
Custom integration
Define typed actions for your own system once and reuse them in every workflow.
Integration SDK
Build the connector you host with a TypeScript SDK that signs requests with HMAC-SHA256 in both directions. Beta.
Provider, action and event counts come from Bondi's integration registry. The Stripe action is the shipped Create Invoice action, shown with a selection of its declared inputs and outputs.
Want to see this on your own process? Our team will walk through it with you.
Walk through your process with usWhat it does
A paid Stripe invoice, a completed DocuSign envelope, an incoming WhatsApp message or a UPS tracking update starts the workflow listening for it, with the event's data attached, so the process moves when the other system does.
Call a one-off endpoint with the HTTP step. For a system every team touches, host a connector in front of your ERP, CRM or internal service and register it once as a custom integration, so every workflow in the workspace reuses its typed actions. The integration SDK, now in beta, handles the signing.
Any workflow can expose a webhook, which you can set to require an HMAC signature, basic or header authentication, and every environment has a GraphQL and REST Data API. On Pro, Service Accounts give a system its own scoped identity.
Decide which system owns each record. A Resolve Record step matches incoming data against your records on up to eight signals you choose. A unique match on an exact signal, such as a reference number, continues on its own, and so does one a reviewer already approved for the same inputs when the step remembers approved choices. Anything else becomes a review task for the workflow's initiator or the users and roles you assign, with up to six preview fields for each candidate. They pick the record or mark it unresolved, and the run continues down that branch. If nobody answers within the window you set, from one hour to 365 days, the expiry branch runs.
Connect a provider once for the workspace. Its credentials are encrypted and stored apart from workflow configuration, and workflow steps reference the stored connection or credential by ID instead of holding the secret.
Under the hood
The mechanisms behind the page, for the architects and security reviewers evaluating it.
Read the technical documentationConnection credentials are encrypted and stored apart from workflow configuration; encryption details are on the Security page. Google, Microsoft 365, Slack and Dropbox actions declare the scopes they need, and the step checks them against the connection's granted scopes first: a missing scope fails the step before credentials are decrypted or the provider is called.
Custom integrations are defined per workspace and resolved alongside the built-in providers. Connectors built with @bondi-labs/integration-sdk sign their requests with HMAC-SHA256 and reject replays outside a five-minute window.
Each provider action call returns one page of results. Pass the provider's page or cursor input to fetch the next page, and filter at the source for large volumes. Retries follow the policy you set on the step.
MCP is a separate, read-only access path for AI clients acting under one named person's permissions. It requires Pro and is in controlled beta.
Designed boundaries
Each built-in provider covers the actions and events in its catalog, not the provider's entire API. Call an endpoint outside the catalog with the HTTP step.
Workflows move data explicitly between systems. There is no background two-way sync to reconcile.
The HTTP step and built-in providers call internet-reachable endpoints only; they block private and internal addresses. A system inside your network sends data in through a workflow webhook set to require an HMAC signature, or through the Data API.
Accounting, ERP and CRM systems connect through their API: the HTTP step with basic, header, bearer, API-key or custom credentials, or a connector you host with the integration SDK and register as a custom integration.
Scope a connection with our teamAvailability
Questions buyers ask
Not as built-in providers. Where the system has an internet-reachable API, call it with the HTTP step using basic, header, bearer, API-key or custom credentials, or put a connector built with the integration SDK in front of it and register it once as a custom integration. Our team scopes the connection with you.
No general sync engine. Workflows move data explicitly: an event or schedule starts a run, and the run calls the actions it needs. That way each change a workflow makes shows up in that run's history.
Yes. Define a custom integration in your workspace, or build a signed connector with the integration SDK, which is in beta.
Encrypted and stored apart from workflow configuration. Workflow steps reference a stored connection or credential by ID instead of holding the secret.
Not directly. The HTTP step and built-in providers block private and internal addresses, so the endpoint must be reachable from the internet. A system inside your network sends data to Bondi through a workflow webhook set to require an HMAC signature, or through the Data API.
Next step
Send us the systems your process touches. We'll mark which connect through a built-in provider, which through their API, and which system should own each record.
