Connect resources

Agent connections tell Workbase which workspace context belongs to an agent. Use connections to make the agent’s working area explicit.

Connectable context

Depending on the workspace, agents can be connected to resources such as inbox channels, objects, apps, integrations, MCP tools, files, folders, records, tasks, notes, lists, skills, and other searchable resources.

The connection has a name, target type, status, and description. The description should say how the resource helps the agent.

Connection statuses

• Enabled: The connection is configured and can be used.
• Connected: The connection represents an active channel or live account.
• Needs review: The connection exists but should be checked before relying on it.

How to choose resources

1. Start with the input

   Add the place where work begins, such as an inbox channel, object, list, or board.

2. Add the source of truth

   Add the object, record type, or list the agent should use when reading or writing context.

3. Add tools carefully

   Add MCP tools, integrations, or apps only when the agent actually needs them for the workflow.

4. Document the purpose

   Write a short connection description so reviewers understand why the resource is attached.

Examples

• Inbound Qualification can connect to Workspace Inbox, a Companies object, and a follow-up board or list.
• Pipeline Follow-up can connect to a Deals object and a task board.
• Account Research can connect to a Companies object, a target account list, and enrichment tools.
• Deliverability Review can connect to Workspace Inbox and relevant deliverability resources.

Troubleshooting

• If the agent misses obvious context, check whether the resource is connected.
• If a resource cannot be found, search for it by title and verify it is visible in the workspace.
• If a connection looks stale, mark it needs review until the owner confirms it.
• If the agent should not act on a resource, remove the connection instead of relying only on prompt wording.

Related guides