integrations
Usage: deepline integrations [options] [command]
Connect providers and manage named workspace authorizations.
Options:
-h, --help display help for command
Commands:
list [options] List named workspace authorizations and their
connection status.
balance [options] <provider> Read a fresh balance using this workspace’s own
provider connection (LeadMagic).
connect [options] <provider> Get a dashboard connection link or connect a
provider with credentials or OAuth.
get [options] <name> Show a named workspace authorization, including
granted scopes.
reconnect [options] <name> Reconnect a named workspace authorization.
disconnect [options] <name> Disconnect a named workspace authorization.
delete [options] <name> Delete a named workspace authorization.
verify [options] <domain> Verify and enable a Google Workspace Calendar
approval.
help [command] display help for command
Explanation:
Purpose:
Set up provider access and manage named workspace authorizations.
providers lists the catalog; tools calls provider APIs; auth handles Deepline login.
Input and output:
connect <provider> returns the setup modal link. My account is the default;
workspace admins can choose Workspace and complete the provider's approval.
list shows workspace authorization names. get <name> shows one record and
its granted scopes. Use the name as connection in a tool call or Play.
reconnect, disconnect, and delete act on existing workspace authorizations.
Pass --provider when the same name occurs for more than one provider.
verify <domain> checks an existing Google Admin grant and enables it locally.
Scope changes require provider approval; a Play's connection selection
cannot expand granted access.
SDK:
client.integrations exposes list, get, connect, reconnect, disconnect,
delete, verify and members. Lifecycle methods accept dryRun and preserve
the same ID/revision checks used by the CLI.
Cost:
These management commands do not spend Deepline credits.
Examples:
deepline integrations connect google_calendar_availability
deepline integrations list --json
deepline integrations get deepline.com --json
integrations balance
Usage: deepline integrations balance [options] <provider>
Read a fresh balance using this workspace’s own provider connection (LeadMagic).
Options:
--json Print the balance and observation timestamp as JSON
-h, --help display help for command
Explanation:
Purpose:
Read the active workspace's connected LeadMagic account balance.
Output:
Provider credits, unit, source and observedAt timestamp. --json returns the same fields
as GET /api/v2/integrations/balance?provider=leadmagic.
Every lookup is fresh; no cached balance is returned on failure. Missing or
inactive BYOK connections fail without using a managed account.
Provider credits are separate from Deepline charges. Tool receipts expose
BYOK facts in responseMeta.provider_usage (legacy meta.provider_usage),
including array results. Missing, invalid and conflicting values are null
with an explicit status; zero means the provider reported zero. Native
X-Credits-Cost and X-Credits-Remaining take precedence over body counters.
Cost:
The LeadMagic credit lookup is free. No Deepline credits are charged.
Examples:
deepline integrations balance leadmagic --json
integrations connect
Usage: deepline integrations connect [options] <provider>
Get a dashboard connection link or connect a provider with credentials or OAuth.
Options:
--link Print a shareable dashboard link
--credentials-file <path> JSON object of credential field names and string
values; keep this file private
--oauth Return an OAuth authorization URL
--preset <id> Server-defined access preset (HubSpot only)
--scopes <scopes> Comma-separated OAuth scopes
--optional-scopes <scopes> Comma-separated optional OAuth scopes
--dry-run Print the proposed setup without saving
credentials or starting OAuth
--json Print JSON without credential values
-h, --help display help for command
Explanation:
Purpose:
Open provider setup or connect provider credentials in the active workspace.
Setup starts with My account; admins can choose Workspace in the modal.
Direct credential updates require a workspace owner or admin.
Input:
With no setup flags, print the dashboard link. --link requests it explicitly.
--link looks up the exact provider id. When a person needs to connect a
provider, use the command printed by deepline describe <tool-id> or look up
the tool's provider field. Give them the returned link and tell them to
select the intended workspace in the dashboard.
The link opens that provider's setup without starting OAuth or saving anything.
--credentials-file <path> saves a private JSON object of credential strings.
A provider that takes one API key reads {"api_key": "..."}; a file with one
field is accepted whatever the field is named. A multi-field provider (for
example a warehouse) rejects a missing field and lists its accepted field
names in the error.
--oauth prints an authorization URL. Open it in a browser signed into the
same Deepline workspace and finish provider consent.
HubSpot: --preset read-crm, update-crm, marketing, sales-sequences, tickets, or all.
all requests every supported capability, including write and admin access.
For custom access use comma-separated --scopes and --optional-scopes instead
of --preset. --scopes must be nonempty; an empty --optional-scopes string
requests no optional scopes. Scope names and presets
are validated by the server; requested access may differ from granted access.
Output:
Link: dashboard URL, or {provider, connect_url} with --json. Share connect_url
with the workspace owner or admin who will finish setup in the browser.
Credentials: confirmation without secret values.
OAuth: URL, or {provider, redirect_url} with --json. This does not confirm a
completed connection. The browser must finish authorization.
--dry-run prints the proposed setup without starting OAuth, reading secret
file contents, or saving credentials.
Cost:
Does not spend Deepline credits.
Examples:
deepline integrations connect hubspot --link --json
deepline integrations connect heyreach --credentials-file ./heyreach.json
deepline integrations connect hubspot --oauth --preset read-crm