Skip to main content
Human guide: task steps and agent prompt → Check the action you want to use before connecting an account. Some tools use Deepline-managed access; others require your workspace’s provider credentials.

Who can manage integrations?

Workspace owners and admins can connect, change credentials, enable or disable, and disconnect integrations. Members can use available workspace connections, subject to the selected action’s access requirements; ask an owner or admin to change the setup. These permissions apply in the web app, CLI, SDK, and API. Provider authorization also requires access to the provider account.

Check the workspace and tool

Use a tool ID returned by search:
Confirm the intended workspace, then inspect connected, credentialStatus, and byok. Required BYOK means the tool needs your own provider account; optional BYOK allows managed access when no account is connected. If the tool lists a byok feature, read its setup instructions with deepline describe <tool-id> --feature byok.

Connect the account

  1. Have an owner or admin select the intended workspace and open Integrations.
  2. Search for the provider and choose Connect. Complete its authorization flow or credential form, including every required field.
  3. Check the connection’s status and use Test where offered. Resolve any reconnect or validation error, then return to the agent to verify access.
Follow the connection form for required scopes and specialized authorization methods. A browser sign-in to the provider still needs to finish the Deepline connection flow.

Verify access

Describe the same tool again in the same workspace. Check connected and any credential error. A successful connection applies only to the actions and access modes that support it. For a live check, review the tool’s inputs and pricing before running a small request; saving credentials alone does not run a lookup. If a request fails with an authorization or scope error, resolve that access failure before retrying. Report it separately from a valid no-match result.
Keep credentials in the connection form or a private credential file, outside chat, Play source, and version control. Setting a provider key in your local shell does not connect it to the hosted workspace.
  1. Inventory dependent Plays, Monitors, identifiers, joins, field meanings, rate limits, permissions, and managed/BYOK requirements.
  2. Compare providers on the same dated records and acceptance rule, including regional coverage and identity inputs. Measure additional accepted results and recorded usage; preserve the original output as the baseline.
  3. Verify replacement access, then switch consumers and check their results. Preserve source and observation time on existing values, and keep a rollback path until the dependent workflows pass.
  4. Review remaining consumers before retiring the old connection. Provider agreements and data-use permissions remain your team’s responsibility.

CRM integrations

For Affinity, Attio, HubSpot, Pipedrive, Salesforce, or Zoho CRM, check the connection’s availability and the selected action’s current contract. Connection access does not authorize arbitrary record changes. Use Repair CRM records for destination IDs, HubSpot properties, Attio attributes, approved changes, and read-back.

Connection availability

A saved connection grants only the actions exposed by the public tool catalog. Google Sheets OAuth can connect an account that owns or can edit a sheet; share that sheet with the connected account when needed. It currently exposes no public google_sheets_* actions. Use CSV input or the Database for a callable Deepline data workflow. Specialized credential procedures are in the shared reference: Meta system user token and external Postgres/Supabase. Next, Choose a prebuilt Play for the task you want to run.