Connectors

Connectors let Agents use external services, such as a payment system, a project-management tool, or a search provider. Configure the connection, choose which Agents can use it, and approve its credential access separately.

Browse the catalog

Open Settings, then Connectors. Catalog comes first in the tab bar. Installed opens when you have configured services. Otherwise, Catalog opens to show the supported services. Proposed and Archived appear when they have entries or you are viewing them.

Catalog lists Task Machine's curated services. Well-known services come first, and more load as you scroll. Search matches service names first, then descriptions and categories.

Choose Install on a service. When it offers both agent access and events, the menu lets you choose Connector or Events. When only one is available, Install opens its setup directly.

Without management access, you can browse without installation controls.

Choose Add connector to open setup. The first choice is Custom or Catalog. Choose Custom to enter your own connection, or Catalog to find a service in the same dialog, then choose Continue.

Native Connectors use the service's own integration. Some reviewed services also offer managed sign-in and tools through Composio. A managed connection does not call the vendor's official MCP server directly. The own-app choice connects directly instead.

Review the publisher, version, website, and source when available. A verified badge identifies an official listing based on the catalog's ownership checks. It is not a security review of every action the service exposes. Community listings remain identified as such. Deprecated and unavailable entries do not appear in Catalog, but an existing connection remains available under Installed until you archive it.

Install a Connector

Review the details

Choose Install on a service in the catalog, then Connector if the menu offers both methods, to open its prefilled Details. Custom starts with a blank form. Check the name and description before continuing.

Choosing a service creates nothing. Confirming Details keeps a Setup required connection and opens its own Connection page. You can return later without losing it. The connection remains unavailable to Agents until you complete setup.

You can keep several independently named connections to the same service. Suggested names avoid names already in use with a numeric suffix. If you enter a duplicate yourself, setup asks you to choose another.

Archived names are available for new connections. Restoring an archived Connector keeps its original name when free, or adds the first available count, such as Google Drive 1. Its identity, saved settings and Agent assignments stay the same.

Catalog Connectors carry their reviewed endpoint or package into setup and select a supported sign-in method. For a reviewed endpoint, Sign-in shows only its documented methods, retaining key, token or public access where supported. Other endpoints keep manual authentication choices when their supported methods have not been established.

Choose how Agents connect

Some services offer more than one way to connect. Details then asks How should agents connect? and preselects the recommended way:

• MCP lets agents use the tools the service offers through an MCP server.
• API makes the service's API capabilities available to Agents. Native connections use account authorization or a saved key and send credentials only to the service's reviewed addresses. Managed sign-in uses Composio's tools instead.
• Command line lets Agents run a reviewed official command-line tool on the Worker. Sign-in asks for its saved token. Task Machine runs the reviewed package at a pinned version, with login and address-override arguments blocked. This option currently covers selected npm tools, not every service's command-line program.

Each Connector uses one way. To use two ways for the same service, install it twice under different names. Choosing another way while editing a Connector asks for its Sign-in again. Native API and command-line connections are checked when an Agent first uses them. Composio-managed connections verify the broker's tool connection before saving.

The Type badges show MCP, API or CLI. MCP includes both hosted servers and MCP commands that run on the Worker. CLI identifies a command-line tool rather than an MCP server.

Connect a service yourself

In Add connector, choose Custom, then Continue, when your service is not listed. Select MCP, API or Command line and enter the connection settings yourself.

• For MCP, connect to a URL or configure a command that runs on the Worker. Hosted connections retain account sign-in and Verification.
• For API, enter an HTTPS base address. In Sign-in, choose a saved key or token and its request header, or public access when the service permits it.
• For Command line, enter an executable already installed on the Worker, with one argument per line. Add a Vault-backed environment variable when it needs a token. The Worker also needs Node.js LTS for command supervision. Task Machine runs your configured command directly, without a shell or automatic package installation.

Setup does not ask for a documentation URL or research the service. Changing the connection method clears the previous method's settings so you can configure the new one.

When feedback is enabled, the first completed setup also requests a catalog addition. The request includes the Connector's name and method, plus normal feedback attribution. Connection addresses, commands, arguments, headers, environment values and credentials are excluded. The implementing agent must find the official documentation and make a reviewed repository entry before the service can join the catalog.

Configure the connection

Finish setup directly on the Connector's Connection page. Connection details and sign-in appear together. Hosted MCP still requires Verification and explicit application of the checked connection. API-key and Command line configurations save without that protocol check. Managed account sign-in still waits for its backend connection check.

In Sign-in, provide the required account authorization or Vault entry. Expand the service's how-to instructions if you need help obtaining a key or creating an OAuth app. Required credentials, callback URLs, permissions, and consent details stay visible outside those instructions. Known catalog addresses and commands do not need re-entering.

Hosted MCP connections are verified from Task Machine itself, without needing a Cloud or Local Worker online. Command-based connections run on the Worker.

Verify and apply

For hosted MCP, Verification checks the connection using the selected authentication and asks it for its available actions. The result applies to the exact draft you checked.

Changing those details, going back, or closing setup requires another check. A failed check must be resolved and retried before applying the connection. Nothing is saved merely because an earlier draft passed.

Native API and Command line save after their required setup is complete, without that protocol check. Composio-managed API connections must pass the broker's protocol check first. For API account sign-in, returning from consent still requires an explicit save for initial setup or changed settings. Successful authorization does not prove that every service action will work.

Choose the Agents

After saving, open the Connector's Agents tab to assign it to one or more Agents. You can also make an active Connector available workspace-wide there. These choices are optional and do not undo the saved connection.

Managing a Connector and assigning it are separate permissions. You can finish setup without assigning when your role permits management but not assignment. People without management access can browse Catalog without installation controls.

Members who can read a Connector open the same page, with saved fields read-only and unavailable actions hidden. A referenced Vault entry appears by name only when you can also view Vault metadata, and otherwise shows as Unavailable. The page never shows a stored secret. Assigning the Connector to Agents follows its own permission.

Manage an installed Connector

Select a Connector's name in Installed to open its page. Its logo, name and status stay visible while you move between Connection, Agents, and Settings.

Connection is where you configure the existing connection. Edit its fields directly, choose saved credentials from the Vault, and select Save changes. The page does not switch the Connector's type. Where account setup is needed, choose Set up sign-in first. Required connection checks open in a dialog. Successful checks let you save the proposed settings. The working connection stays unchanged until you save.

Agents shows assigned and unassigned Agents in one list. Each access switch saves immediately. The workspace-wide switch above the list also saves immediately. When it is on, every Agent has access and individual switches are replaced by Workspace access. Existing individual assignments are kept for when you turn workspace-wide access off. Credential grants remain separate.

Settings holds its name, description, external-spending permission and Archive. Each editable section has its own Save action. External spending is disallowed by default. Turning on Allow external spending lets authorized Agents spend through that connection without a separate spending approval. Other checks still apply. It is not a spending cap or a credential grant.

The Installed row's Allow external spending / Disallow external spending shortcut changes the same permission. Changing the destination or account revokes it. Renaming the Connector does not. Events Connectors have Connection and Settings but no Agents tab or outgoing-spending permission.

Receive events from a service

An Events Connector receives events from a service, such as a new pull request review or a paid invoice. They can start Workflows or make a Task's next step ready. It never connects Agents to the service, so it has no Agents step and its Type badge reads Events. Add it separately even when the same service already has an MCP, API or command-line Connector.

In Catalog, choose Install, then Events when both choices appear. An events-only service opens its setup directly.

You can also choose Set up events in the command center, or start setup from a workflow's Add trigger dialog without leaving it.

• Details names the Connector and, when the service offers several kinds of events, asks which ones to receive. You can choose several.
• Sign-in has a section for each chosen kind. When the service can send a kind in more than one way, such as Stripe's full or minimal event content, it asks how the service should send them. Each option says what it means, and the recommended one is selected. Choose the same option in the service. It asks how to set it up when the service offers a choice. Automatic lets Task Machine set up the events in the service with an API key. Manual shows a private link to add in the service's settings. Either way, that service's own steps, such as where to paste the link and where its secret comes from, sit collapsed below. Add to Task Machine asks for the Vault entry of each secret the service uses, such as its signing secret. If the service doesn't sign its events, you must turn on Accept events without a signature.

To receive another kind of events later, open the Events Connector's Connection page and select it. Kinds the Connector already receives keep their link and how the service sends them.

Task Machine checks every event exactly as the service documents, for example its signature, before storing it. Events that fail the check are rejected, cost nothing and never start a Workflow or release a Task's waiting step. Each event it accepts costs $0.005 or €0.005 from your usage, as Usage and fees explains. The Connector gets lasting access to its secrets so it can check events without a running Agent. Revoking that access or archiving the Connector stops it from receiving. A Task already waiting for an event keeps its scheduled check.

With Automatic setup, Task Machine sets up the events in the service when a Workflow Trigger or a waiting Task needs them. It combines their event selections where the service supports selecting events, and removes the setup from the service when you archive the Connector.

If an attempt was interrupted and the service may already have the setup, Task Machine does not repeat it. When an attempt fails in a way only you can fix, such as a rejected API key, the Connector's row shows a warning and Connector managers get one Inbox item saying Task Machine couldn't set up the Connector. Choose Fix connector in that item, or Edit in the row menu, check the service for a duplicate or replace the key, then choose Try again. The Inbox item clears once events can arrive again. Edit also shows the link and when the last event arrived.

An Agent can propose an Events Connector when its work needs to wait for a service's events. After the proposal is approved, whether by you or automatically, you still finish the setup yourself: its row shows Setup required with a Configure button, and an Inbox item asks you to set it up, where Set up connector opens the same setup.

Events cover the services and event kinds whose delivery Task Machine has reviewed. Other services do not offer Events installation yet.

Choose authentication

Connect an account

Choose Sign in with your account, then the Sign-in footer action to open the service's consent screen. Hosted MCP uses Verify connection and returns to Verification. An API account uses Sign in and returns to Sign-in for any remaining credentials and an explicit save. Cancelled authorization returns to Sign-in so you can try again.

Task Machine seals the authorization until you apply setup, when its Vault entry is marked Managed by Connector. Manage access grants in Vault and change the login through the Connector.

Use managed sign-in

New Google Drive, Gmail, Docs, Sheets, Slides, Calendar, Slack, YouTube, LinkedIn and Google Search Console connections use Composio when you choose Sign in with your account. Sign in to the service and approve its requested access. You do not need a Composio account. GitHub keeps Task Machine's native OAuth app, and services with supported automatic registration retain that native path.

Composio holds and refreshes the service's tokens and processes tool requests and results under a Data Processing Addendum. Managed Connector calls use zero data retention, so their arguments and results are not stored in Composio's execution logs. Connection credentials, operational metadata and temporary files have separate retention rules. Read the Privacy Policy and Subprocessor Schedule for those rules and how this differs from Task Machine's managed-AI settings.

Finish managed consent in the tab where you started it. That tab keeps temporary connection-attempt context. Missing or expired context requires restarting Sign-in. Verification and Apply still follow account consent.

Use your own OAuth app remains the second card. Follow the service's guide, register Task Machine's displayed callback URL and permissions, then enter your Client ID and secret. Task Machine stores those credentials in Vault and connects directly to the service, without Composio. Reopening or retrying a saved own-app connection does not show or require resubmitting its secret.

Choose Google access

Google Workspace offers account authorization only, without API-key or no-sign-in cards. Contacts, Google Chat and Workspace Search require Use your own OAuth app for new connections. Follow the existing guide with a Google Cloud project you control. Your app remains subject to Google's applicable verification requirements. An eligible personal-use or company-internal app can have different requirements from a public app.

Existing native connections keep their provider and permissions until you choose Disconnect. The next Sign in with your account uses the service's current Catalog default, including Composio where offered. Use your own OAuth app always connects directly. Catalog changes alone never switch a saved login.

Read the access summary on a saved native Google connection:

• Drive works with files Task Machine creates. Existing files and folders need your own Google app. There is no file or folder picker in this setup.
• Chat can send messages and list spaces and members, without reading message history.
• Workspace Search searches Calendar events only. Searching Drive, Gmail or Chat needs your own Google app.

Reconnect required identifies an older native Task Machine login with permissions outside the current limits. Choose Log in again and verify the replacement before using it again. Saved native connections continue their native sign-in path. The stored login is replaced only after Verification succeeds, with existing assignments and access grants retained.

Connect social and search accounts

YouTube and Google Search Console offer managed account sign-in or Use your own OAuth app. The own-app choice authorizes and calls Google's API directly. X requires your own OAuth app and connects directly to X. Task Machine does not supply its app registration.

LinkedIn offers managed account sign-in or Use an API key or token. For the direct path, obtain an access token through your own LinkedIn app and save it in Vault. TikTok uses the same direct Vault-token setup without a managed sign-in option. Renew those tokens through your own app when they expire. Task Machine does not automatically refresh these manually supplied tokens.

Connect Google Ads or Meta Ads

Google Ads uses your own Google OAuth app under its current access policy. Follow the instructions in Sign-in, authorize the account, then select a Vault entry for your Google Ads developer token before saving. An Agent can supply the account's non-secret manager customer ID when a request needs it. Other Google Connectors keep Task Machine sign-in wherever their access policy permits it.

Meta Ads asks for a saved access token. Both Ads connections use their official services. Their Playbooks still require approval before launch or increased spend.

Use a key or token

For an API-key service, select the required request header and its Vault entry. Keep the header name, value prefix, and credential together.

Choose No prefix when the service expects the stored value unchanged, Bearer when its authorization header requires that scheme, or the service's documented custom prefix. A selected prefix is separated from the stored value by one space. It does not alter the Vault entry.

The Vault picker can create a write-only entry without closing setup and selects it immediately afterward. Connections that run on a Worker can instead map Vault entries to the environment variables their command expects.

Use a public endpoint

Choose no authentication only when the endpoint is intended to be public. Authentication choices are exclusive: an account login does not compete with a manually configured authorization header. A reviewed API can require a separate supplemental credential, such as Google Ads' developer token, alongside account authorization.

Credential values are resolved for the connection check and later authorized use. They do not appear in verification results.

Grant only the access the Agent needs

Assigning a payments Connector to a finance Agent does not give it to every other Agent. Each Agent receives its explicit assignments plus active Workspace-default Connectors. Task Machine does not install a web-search provider as a Workspace default.

Assignment does not silently grant Vault access. Required credential decisions appear in Inbox, where an authorized person can approve the applicable one-Run, timed, or ongoing access, or reject it.

If work reaches that connection before the decision, the original Run waits rather than repeatedly retrying. The same decision and its outcome remain visible in the blocked Chat or Task Activity. Chat keeps the composer visible but unavailable while access is missing.

Approval continues the preserved work. Rejection stops it and blocks affected Tasks until the assignment or access is changed. See Vault for the credential flow.

Review an Agent's proposal

An Agent can propose a missing Connector from Chat before attempting work that depends on it. Review its rationale, authorize the service when required, and choose its assignments so the original request can continue.

The Proposed list shows the service, connection type, and proposing Agent. Select a row to open the full proposal. Connector managers can choose Approve or Reject from its ⋯ menu.

The preview also keeps both decisions. Rejection asks for a reason. Approval opens connection setup and keeps the Connector Setup required until you finish. It does not authorize credentials or make the connection available to Agents.

Change a Connector through Chat

Ask an Agent in Chat to revise a Connector, such as changing its description or connection settings. Autonomy decides whether the proposal waits for your approval or applies automatically. A waiting proposal leaves the accepted configuration unchanged, and you can review it in Chat or Inbox.

Connector changes proposed as part of a Playbook remain in that Playbook's shared review. Credential setup still uses the secure forms described above.

Check or reconnect an existing connection

For an active hosted MCP Connector, choose Test connection on its Connection page or Check connection from its row menu. Results open in a dialog without changing the saved connection. A temporary service or network problem can be retried from that dialog.

When a managed Connector call fails, the agent receives a diagnostic reference and whether the action was attempted. Include that reference when contacting Task Machine support. A failed call alone does not mean you need to sign in again.

If the action may already have run, check the service before trying again. Task Machine does not automatically replay the failed managed call.

An expired account login can produce a warning and a Log in again action. The same action is available in the corresponding Inbox recovery request or on the Connector's Connection page. Authorization returns you to the originating place, where Task Machine checks the new login before saving it.

Reconnect preserves the sign-in path you already used. An incomplete saved managed connection is a setup error to retry, not a reason to create your own app. A saved own-app login stays on its existing path until you disconnect it. Choosing managed sign-in afterward requires a new verified login.

A login-only reconnect applies automatically after its authorization checks succeed. Hosted MCP and Composio-managed connections also require protocol Verification. Native API account recovery does not run that probe. When the Connector already has a managed Vault entry, that entry and its existing access grants stay the same. Retry a failed check or start another login from that same surface.

Shared older entries and entries that cannot be safely identified as belonging only to this Connector remain untouched. Reconnecting creates a new managed entry instead, which may need access approval. Initial setup and changes to connection settings still require explicit Apply.

A failed or cancelled attempt keeps the previous stored login and settings. The service may still invalidate an earlier authorization, so this does not guarantee that the old login remains usable. Archiving retains the login and grants. Disconnect stops local use and moves the managed Vault entry to Trash. Native connections attempt provider revocation. Composio connections retire locally first and remove the provider account in background cleanup. This does not promise deletion of Composio's earlier execution logs.

If the login expires after an Agent has already started work and its provider session can be preserved, Task Machine preserves that exact Run and its current work. After you log in again, the Agent continues its existing session without automatically repeating the rejected Connector action. When the earlier action might have changed remote data, the Agent checks durable state and asks for confirmation before an uncertain retry. If no resumable provider session is available, the Run fails rather than claiming it can continue safely.

Task Machine normally renews short-lived account access automatically. An access token reaching its expiry does not by itself require another sign-in.

Task Machine keeps one recovery request for each authorized Connector manager rather than repeatedly asking about the same rejected login. A successfully verified and saved login clears those requests. Temporary provider, network, encryption, and save failures remain retryable errors rather than unnecessary login requests.

If an earlier setup failed to save its managed connection correctly, Task Machine can restore the existing authorization without asking you to sign in again. It first checks the original approval, current management access, saved credential and service account. A disconnected account or a changed login is never restored this way.

Check connection is not available for API or command-based connections.

Some catalog Connectors run a pinned package through npx on the Worker. Managed Cloud Workers include it. On a Local Worker, install Node.js LTS first. Without it, the Run stops and Inbox shows the steps to install the missing command.

Keep repository access separate

The catalog includes official GitHub, GitLab, and Bitbucket provider Connectors for pull requests or merge requests, reviews, issues, and CI. Each uses the provider's own hosted endpoint and starts with account authorization.

Repository SSH access handles Git transport, not those provider actions. Configure it separately in Coding Work.

Choose search providers deliberately

Providers such as Exa are optional catalog Connectors. Install and configure the provider you choose, then assign it where needed. Its processing terms remain separate from Task Machine's managed AI requirements. See Privacy and data.

Browser access is separate from Connectors. Task Machine supplies the browser for a Run when the Agent's settings permit it.

Connect an email provider

An email Connector lets an Agent work with an email service you already use: send mail, read what arrived, or check delivery results. Search the Catalog for email to see the supported services, such as AgentMail, Mailgun, Postmark, Resend, SendGrid, Brevo, MailerSend, SparkPost, Mailtrap, Bird and SMTP2GO.

Each service uses the connection its vendor documents:

• AgentMail, Resend, Brevo, MailerSend, SparkPost and Bird connect to the vendor's hosted MCP server. AgentMail and Resend accept an API key or account sign-in, Brevo accepts a key, and the others use account sign-in.
• Mailgun and Mailtrap run the vendor's own MCP package on the Worker. Their Connection step maps one Vault entry to the environment variable that carries the key, MAILGUN_API_KEY for Mailgun and MAILTRAP_API_TOKEN for Mailtrap. Mailtrap's account-level tools need a second value that setup cannot map, so that connection covers sending and sandbox testing.
• SendGrid, Postmark and SMTP2GO connect to the vendor's API with a saved key.

To connect AgentMail with an API key:

1. In the AgentMail Console, create an API key. Limit it to one inbox or to read-only access when the Agent does not need more.
2. In Connectors, choose AgentMail from the Catalog and confirm its Details.
3. In Sign-in, choose Use an API key or token. AgentMail's x-api-key header is already selected. Pick the key's Vault entry, or create it there without leaving setup.
4. Run Verification, apply it, then assign the Connector to the Agents that should use it.

Other email services follow the same steps with their own key or sign-in. Create the key in the provider with the narrowest permissions it offers.

An Agent can then use whatever the provider's tools allow, such as creating an inbox, reading and searching messages, sending or replying, or looking up why a message bounced. Treat mail the Agent reads as untrusted input from outside senders. Messages to people outside Task Machine follow the Agent's Autonomy settings, so you decide whether it asks first.

A catalog entry is not an approval of the provider's terms. You choose the provider and hold the account, so it acts under your own contract with its own regions, retention and training rules, and it is not a Task Machine subprocessor. Task Machine supplies neither the account nor its credentials. Read the provider's terms before mail content reaches it, and see Privacy and data for how Connectors differ from Task Machine's managed AI settings.

If your account runs in a provider's EU or enterprise region, its address can differ from the one in the Catalog. Choose Custom and enter the address from the provider's guide.

Finish the connections a Playbook needs

A Playbook can bring its Connectors and Agent assignments as part of the setup. After a proposed Playbook is approved, an Inbox follow-up for each Connector asks you to finish its connection before the work uses it.

Use Skills for reusable expertise rather than service access. See Members and roles when a management or assignment action is unavailable.