Integrations
Explore 1,000+ cataloged app and cloud-service providers.
7,621 documented node types, 84 of them triggers, each with a schema-driven form and health pre-flight; a connection test where the provider offers one. A service with no typed node is reached through the HTTP node using the connection you already hold, or can be requested from the AI builder.
What the numbers count
- Providers · 1,075
- A provider is one cataloged connection target with its own page — an app, an AI vendor, a database or a single cloud service. 728 of them are individual cloud services, each counted as one provider: 394 Amazon Web Services, 152 Google Cloud and 182 Microsoft Azure. The other 347 are apps, AI vendors, databases and developer tools. A provider is not an app count and not a node count.
- Node types · 7,621
- Every node type with a published contract and a reference page. 7,378 are listed on a provider page as operations or triggers; the other 243 are core node types — control flow, data, AI, files, vectors — that need no connection and sit under no provider. An operation is a step a run performs, such as sending a message or reading a row.
- Triggers · 84
- Node types that start a run. They are included in the node-type count above, not added to it.
- Connection test
- “Connection test available” means a stored credential can be checked against the provider when you add it. It is not a record that a test was run or passed.
- Catalog
- Synced from the product’s own public catalogue, version 668a0cb515f936bd, refreshed on .
Business apps · JWT · 0 providers
No provider or operation matches these filters. It is probably still reachable: the HTTP node calls any REST API with a stored credential, and the AI builder can request a new app for you.
Request an integrationDon't see your app? Ask for it from inside the builder.
Describe the workflow to Build with AI. Any app it cannot find becomes a stand-in node and a request our team sees the same day.