Integrations
An integration is a set of node types beyond the built-ins, together with the connection those nodes depend on. Add the connection once and every node in that integration can use it—a Jira connection is what lets a Jira trigger start a flow and a Jira action act on an issue.
Nodes lead. What an integration gives you is the triggers and actions it adds to the picker; the connection is the dependency those nodes declare, and it is documented at the end of each integration's section. A few integrations need no connection at all, and a few provide a connection with no nodes of its own yet.
For what a connection is and how you create one, see Connections.
What each integration adds
| Integration | Nodes | Connection |
|---|---|---|
| Brightspot CMS | Content trigger; Content, Content Query, Content Fetch, Content Script, and Remote AI Agent actions | Brightspot |
| GitHub | GitHub trigger; GitHub action, with 22 operations | GitHub |
| Jira | Jira trigger; Jira action, with 12 operations | Jira |
| Slack | Slack Message action; also a channel human-in-the-loop questions are asked and answered in | Slack |
| Microsoft Teams | Teams Message action; also a channel human-in-the-loop questions are asked and answered in | Microsoft Teams |
| Email action | None—delivery is configured by an administrator | |
| OpenAPI | OpenAPI action | None—each step names the specification it calls |
| AWS | AWS AgentCore action | AWS, which is also an AI provider account serving Bedrock models |
| Azure | Coming Soon | Azure, an AI provider account |
| Coming Soon | Gemini and Google Cloud, two AI provider accounts | |
| OpenAI | Coming Soon | OpenAI, an AI provider account |
Integrations that only bring a connection
Azure, Google, and OpenAI each provide a provider account for AI rather than nodes of their own. Point the built-in AI Agent action or AI Judgment condition at one of those accounts and the step's work runs on it—the tokens land on your bill, and your content travels only to the provider you chose. Dedicated nodes for those providers are Coming Soon.
AWS is both: an account that serves Bedrock models to AI steps, and the account the AWS AgentCore action invokes hosted agents through.