Skip to main content
Beta: Agents isn’t available in every workspace. To try it, contact the Pipedream team. Give an Agent access only after testing your Okta integration.
An Agent is an application you operate, such as a backend service or hosted assistant. Conduit decides which tools it can use and for whom; its code, model and hosting stay with you. The Agent signs a person in at Okta and sends Conduit that person’s Okta access token.

Add an Agent

  1. Have a workspace owner turn on Agent access for your Okta sign-in provider.
  2. As a workspace admin, open Agents, select Create agent, and enter a name and optional description.
  3. Have an owner open the Agent’s Authentication and enter the Agent OAuth client ID of the Agent’s own Okta app.
  4. Choose its Tool access and Delegation, then switch the Agent on.
A new Agent starts switched off, with no tools and nobody to act for. It acts for a person through their own Conduit account, with the tools they’ve turned on and the accounts they’ve connected on Home. It can’t change their tool choices or administer Conduit. If Agents says external agent access is off for this instance, ask your instance administrator to switch it on.

Pause or stop an Agent

Switch the Agent off to pause it; switching it back on accepts its unexpired tokens again. To stop it acting for one person, take them out of its Delegation. Delete the Agent to remove it and its configuration. Each change, and each tool call an Agent runs, appears in the audit log.