Getting Started With Integrations
Connect Builders workflows to email, storage, messaging, queues, issues and remote systems.
Basic integration flow
- Open the integrations page.
- Choose an integration category and provider.
- Fill the required fields.
- Enable MCP access only when the integration should be available to AI tools.
- Test the connection if a test action is available.
- Assign the integration to yourself or a team.
- Save it and use it in compatible blocks.
What each integration unlocks
Every integration page should answer three questions before it is used in a workflow: which credentials are required, which operations are possible, and which Builders blocks become available. If a block asks for an integration selector, it only lists integrations owned by the current project owner or team and compatible with that block family.
Ownership and access
Workflow resources are scoped by project owner. User-owned projects use user Vault resources. Team-owned projects use team-owned resources. Private member integrations are not exposed to team workflow drafts.
MCP usage
MCP is the tool layer used by the AI Assistant and AI-capable runtime features. When Allow MCP usage is enabled for a supported integration, Builders may expose tool calls such as googleDrive.*, oneDrive.*, s3.*, smtp.*, imap.*, queue.*, issue.*, twilioSms.*, signal.*, whatsappBusiness.* and similar provider tools. MCP does not create workflow blocks by itself. It makes the integration available to assistant/tool execution after the connector supports that provider and the workflow has access to the integration scope.