AgentBlackBox / Connected apps & tools

Connect the tools your agent uses

Route actions from connected apps and custom tools through the same workspace rules.

01

Five connected apps

Gmail sends a message to one recipient. Slack posts a message, GitHub adds an issue or pull-request comment, Google Drive shares a file, and Notion appends content to a block.

Authorize each connection in Apps → Connected apps. Existing read-only connections need the appropriate write access before an agent can perform a write.

02

Register an agent and its tools

Give an agent a name, risk class and list of permitted tools. A workspace can disable an agent or restrict a key to it. Custom HTTP endpoints and MCP servers use the custom-tool gateway and must have public HTTPS addresses.

03

Choose where the action runs

An agent that executes its own action first requests a decision, follows that decision, then reports the outcome. For a connected app or registered tool, the appropriate gateway checks the rules and carries out an allowed action.

An action that can execute needs an API key bound to the agent. The agent gets the decision while AgentBlackBox holds the connected app’s credentials.

The REST API returns a request ID that support can use to trace an error. The documentation also covers scoped keys, gateway rate limits, signed incoming webhooks and the TypeScript client available in the source repository.

KEEP EXPLORING

Records & reports

Review the events behind a task, changes to workspace settings, and the evidence available for export.

Continue reading