Skip to content

Integrations

Work with the apps your clients already use.

Start a workflow when something happens in one app and act in any other, on each client’s own account. Every request is watched like the rest of the workflow, so you hear when an app stops answering.

Get early accessSee pricing

Thrum opens soon. Sign up now and you’ll be among the first in.

apps
37apps
with ready-made steps
32with ready-made steps
actions
70actions
triggers
53triggers

Every app

37 apps shown

CRM and email lists 8

Messaging and email 8

Tasks and projects 5

AI models 4

Support 4

Data and docs 3

Payments 3

Scheduling 1

Automation 1

Triggers

Something happens in the client’s app, a new deal, a paid invoice, a booking, and the workflow starts. By webhook where the app sends one, by checking where it does not, with a daily check that the webhook is still on. App triggers are in beta.

Actions

A step for one app with its own fields: post the message, create the contact, add the row. Values from the run go in by name, so there is nothing to write by hand.

Built-in and Via HTTP

Texts and email are steps of their own, through the client’s Twilio and Resend. Anything else with an API and a key is a web request, and the common ones come as ready recipes.

Any API

An app not on the list is a web request step.

The web request step reaches any HTTPS API: your method, address, headers and JSON body, values from the run read by name, and the client’s key kept as a credential.

An app that only allows sign-in with OAuth cannot be reached this way yet.

What Thrum does on every request

A failing request
Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause
Given it, up to an hour
Requests at once, per account
2, per worker; the rest wait their turn
Timeout
15 seconds, unless the step sets its own
Private and internal addresses
Refused, on every redirect too
The client’s key
Encrypted, bound to the client, and kept out of every run record
A step that keeps failing
Marks the workflow Degraded and alerts you, not the client

Questions about integrations

Whose account does each one use?

The client’s. Every key is the client’s own, stored encrypted and bound to that client, so one client’s workflow can never use another’s key. Thrum copies no key between clients, not even from a template or a pack.

Can a workflow start from something in one of these apps?

Yes, in beta. 53 triggers start a workflow from something that happens in the client’s app, by webhook where the app sends one and by checking where it does not. Each app’s page lists its triggers.

Which parts are in beta?

App triggers, and most app actions. Beta means the module is built and tested, and hasn’t yet run against the live service it depends on, such as Stripe or Twilio. The tag comes off once it has.

What if an app I need is not listed?

If it has an API that takes a key or a webhook address, a web request step reaches it, and Thrum retries it, keeps the key out of the run’s record, and tells you when it keeps failing.

What happens when an app stops answering?

The step is retried for errors a retry can fix, a pause the app asks for is honoured, and a step that keeps failing marks the workflow Degraded and alerts you. Your client is not told.

App names and logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied. Google Sheets is a trademark of Google LLC. Airtable is a registered trademark of Formagrid Inc dba Airtable.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early accessSee pricing