Skip to main content
Dench brokers external tools through dench tool. Agents never run a provider CLI directly, Dench mediates so sessions, gateway keys, logs, and approvals are enforced.

GitHub

Gmail

Stripe

Linear

Slack

Notion

Calendar

…and more

​
Connect a tool

1

Check status

dench integrations lists every connected app. Gmail, Outlook, Calendar and LinkedIn connect through Dench itself, so they appear with source: "dench"; apps you connect from the catalog appear with source: "app". Check them with dench tool status gmail --json (or outlook, linkedin, calendar). calendar shows both Google and Microsoft calendars; google-calendar and outlook-calendar filter by provider. If nativeAvailable is false, the lookup failed; that does not mean the account is disconnected.
2

Start the connection

For Gmail, Outlook, LinkedIn, or Calendar, use the same command with gmail, outlook, linkedin, or calendar. These return a Dench sign-in link using the web app’s configuration and managed callback. Sign in as a workspace member or use a member-owned Dench API key.Share the returned redirectUrl as Markdown, e.g. [Connect Gmail](<url>), ask the human to authorize the account, then run the matching status command again. Slack keeps its in-house install URL (dench tool connect slack, org admin); other toolkits connect as connected apps. --callback-url is only supported for connected apps.
3

Find the right tool

4

Run it

​
Read-only vs gated

Run directly

Slugs containing FETCH, GET, LIST, SEARCH, READ, or FIND are read-only and run without a separate approval.

Needs approval

Connected-app actions with their own approval policy return an approvalId. Get a human yes/no, then rerun with --approval <id>. See Approvals.
Dench-brokered Slack, Gmail, Outlook, Calendar, and LinkedIn tools use the fixed workspace Full access (yolo) policy: no approval request or --approval is needed, including for workspaces with older saved ask preferences. There is no Approvals setting. Authentication and connection access checks still apply. Explicit approval APIs and existing approval records are unchanged.
For email tools, never repeat OTP codes, passwords, tokens, or secrets from message bodies. Prefer sender, subject, date, and short snippets.
Connected-app tool operations are also available over the API under /tools. People and company search use /crm/people/search and /crm/companies/search. Try them in the API playground.