Overview

A Connector is a maintained integration to one company system: Slack, Jira, Salesforce, Google Drive. Merge builds and tests it, keeps its tools working across the vendor’s API versions, and tunes each tool’s description so a model picks the right one instead of guessing.

Authorizing a Connector does not give anyone access to it. It makes the Connector available to your organization. Tool Packs decide which of its tools exist as a bundle, and Groups decide which employees get that bundle.

Hundreds of Connectors ship ready to use. The full catalog, tool by tool, is at Connectors.

Browse the catalog

Connectors in the Workforce console is your organization’s catalog. Search by name, or filter by configuration status to find the Connectors that still need you.

The Ready to use filter is the one to reach for when you want everything an employee could connect today, which is every status except Action required.

Authorize a Connector

Open a Connector from the catalog and it has up to three tabs.

Most Connectors work without touching Application Credentials: employees authenticate against Merge’s OAuth app, and their consent screen names Merge. Register your own when you want the consent screen to name your company, rate limits scoped to your own traffic, or a smaller scope set than the default. A Connector marked Action required ships with no shared OAuth app at all and authenticates nobody until you add one. See Application credentials.

Whose credentials the call runs under

Nothing runs as a service account. The first time an employee’s AI reaches a Connector, the employee authenticates it themselves, and the token Workforce stores is theirs. A Jira call from their agent lands as that person, with the permissions Jira already gives them, and appears in Jira’s own audit log under their name. Revoke them in Jira and the calls stop, whatever Workforce says.

That is the property most of your access model rests on: your existing per-system permissions keep holding without being restated here, and an employee’s AI can never reach further into a system than the employee can.

Grant access to it

Authorizing a Connector and granting access to it are separate steps, in this order:

1. Authorize the Connector, adding Application Credentials if it needs them
2. Add it to a Tool Pack and pick the specific tools you want exposed. Most Connectors expose dozens.
3. Assign that Tool Pack to a Group from your identity provider

An employee whose Group grants the Tool Pack sees those tools on their consent screen the next time their client lists tools. Ask for a tool outside that set and the call fails, then surfaces in your dashboard as an access request you can approve.

Next steps