Integrations

Bind a workspace Integration into a Project so the Workflows and conversations in it can use it. You add an Integration that a team admin or workspace admin has already connected.

Audience: builders

The two paths

Add a Team or Workspace Integration. A Team Integration is available to every Project in that team, and a Workspace Integration is available to Projects across the workspace. In the Project context, open Integrations, pick the Integration, and select Add to project. You do not sign in to the provider. Being available does not add an Integration to any Project automatically.

Ask an admin to connect a new one. You cannot create a new personal Integration. When the Integration you need is not available, ask a team admin to connect it for your team, or a workspace admin to connect it for the whole workspace. Personal Integrations you connected earlier keep working, and you can promote one to a team or the workspace if you are an admin there. See Credentials, bindings, and ownership.

Who connects each provider is named on that provider's setup page. Visit Integrations and pick the provider.

What each capability brings to the Project

Once an Integration is bound, your Project can use any of the Integration's lit capabilities:

• Read. A Workflow or a conversation can read content from the Integration.
• Write. A Workflow can save content back to the Integration.
• Triggers. The Integration can kick off a work item for your Workflow. Configured under Workflows > Triggers.
• Reply. Your agent can send messages back through the Integration (such as Slack thread replies).

The set of lit capabilities is provider-defined, not per-Project. A binding cannot grant a capability the Integration does not support.