> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Add and manage Deepline integrations in the workspace UI.

[Human guide: work with your agent →](https://deepline.com/docs/human/integrations.md)

> [!NOTE]
>
> Connect one provider account, then inspect the action you intend to use.

Add integrations in the [Integrations page](https://code.deepline.com/integrations).
The UI walks you through the provider-specific connection, authorization, and
validation steps.

Once connected, an integration is available to the applicable Plays, Monitors,
and workspace tools. Use the integration’s guide below when you need its
supported actions, inputs, outputs, or operational details.

> **[Open Integrations](https://code.deepline.com/integrations)**
>
> Add or manage an integration in your Deepline workspace.

## Connect a provider account

1. Open Integrations in the workspace you want to use. You must be an owner or admin.
2. Select the provider and complete its current credential form or OAuth flow.
3. Supply every required field. Icypeas, for example, asks for both an API key and API secret.
4. Confirm the connection succeeds, then inspect the tool you plan to run with `deepline describe <tool-id> --json`.

Use the provider-specific setup guide for scopes, permissions, and specialized
connection flows. See [Provider credential reference](https://deepline.com/docs/features/bring-your-own-keys.md)
for the workspace and API contract. Local provider environment variables do not
connect a provider account to the hosted workspace.

## Review access and dependencies before changing a connection

1. Identify the workspace, provider account, connection owner, and workflows
   that depend on it. Inspect each relevant action's supported access mode.
2. Use the provider-specific form or OAuth flow to change credentials or scope.
   Keep credentials out of Play source, prompts, and tool payloads.
3. Inspect the current action contract and test only the bounded work needed to
   confirm access. A successful connection does not validate every action.
4. Review affected consumers before retiring access. Preserve uncertain failures
   as access errors rather than reporting that the source has no matching data.

The team's provider inventory, agreement review, renewal schedule, and internal
approval policy remain team-owned processes. A connected account does not
replace those processes or authorize every downstream use of its data.

## Related guides

> **[CRM integrations](https://deepline.com/docs/features/crm-integrations.md)**
>
> Connect Salesforce, HubSpot, Attio, and other CRMs.

> **[Email sequencer integration](https://deepline.com/docs/features/email-sequencer-integration.md)**
>
> Sync with outbound sequencing platforms.

> **[Waterfall enrichment](https://deepline.com/docs/features/waterfall-enrichment.md)**
>
> Build multi-provider enrichment workflows.

> **[Advertising audiences](https://deepline.com/docs/ads-audiences.md)**
>
> Sync audiences to Google Ads, Meta Ads, and LinkedIn Ads.

## Verify this task

Confirm the connection in the intended workspace. Describe the selected tool and inspect required inputs and supported access mode.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.