Skip to main content
Use a sequencer integration after you have reviewed the people, campaign, and message you intend to send. Deepline can read and write supported sequencer resources; it does not decide who may be contacted or activate a campaign on your behalf.
Adding a lead, changing a sequence, and activating a campaign can create external side effects. Resolve the campaign first, pilot a small approved batch, inspect the provider response, then activate only with explicit approval.

Choose the sequencer you already use

The current integration catalog lists these sequencers. Each card opens its provider guide, which is generated from the live catalog or maintained beside the provider contract.

Amplemarket

Prospect, manage accounts, and add qualified contacts to sequences.

EmailBison

Inspect campaigns, senders, replies, lead state, tags, and warmup first.

HeyReach

Add reviewed LinkedIn profiles to an existing campaign.

Instantly

Manage email campaigns, lead batches, activation, and campaign reporting.

Lemlist

Build multi-channel email and LinkedIn sequences with explicit review.

Nooks

Inspect sequences, prospects, calls, tasks, and mailboxes in a sales-engagement workspace.

Outreach

Work with prospects, sequences, mailboxes, and rep activity through OAuth.

Salesforge

Manage connected sequences, contacts, mailboxes, and webhooks.

Salesloft

Inspect and manage cadences, people, activity, and workflows with your key.

Smartlead

Control campaigns, senders, schedules, sequences, leads, and analytics.

Choose by workflow

Each provider has its own current contract. Search and inspect the exact action before you build a write step:
Use the returned campaign ID and the displayed schema for later writes. Do not guess a provider field from another sequencer’s API.

A safe activation pattern

  1. List or read the existing campaign. Confirm its ID, owner, schedule, and sending state.
  2. Build a small approved lead batch. Keep the source, qualification result, and intended campaign visible to the reviewer.
  3. Add the batch and inspect the returned accepted and failed rows. When your workflow requires deduplication, explicitly read the relevant existing leads or provider lookup first; Deepline does not promise cross-campaign or cross-provider deduplication.
  4. Review the sequence and schedule in the provider. Activate only after that review.
  5. Read campaign stats after a controlled send. Treat the provider’s results as the source of truth for delivery and engagement.

Instantly

Use Instantly for a compact email-campaign loop: list or create a campaign, add or update leads, control campaign state, then review stats. Deepline supports campaign reads, creation, duplication, activation and pausing, lead listing and patching, and campaign metrics.
Before creating a campaign, read an existing campaign with instantly_get_campaign and reuse a provider-supported timezone and schedule shape. Keep activation behind your enrichment and review gate. Recommended prompt:

Lemlist

Use Lemlist when the sequence itself is part of the workflow. Deepline supports campaign creation and updates; sequence-step reads, adds, updates, and deletes; lead insertion and state changes; activity and inbox reads; messages; webhooks; and unsubscribe operations.
Sequence delays are in days. Campaign create and update responses include a web_url; use it to review the sequence in Lemlist before starting it. A duplicate conflict returned by Lemlist is an outcome to inspect, not proof that every prior campaign is deduplicated. Recommended prompt:

HeyReach

Use HeyReach for LinkedIn activation into a campaign that already exists. Its public API integration intentionally stays narrow: list campaigns, add contacts, and read campaign stats. Create the campaign in HeyReach first.
Recommended prompt:

Smartlead

Use Smartlead when you need programmatic control beyond a lead push. Deepline supports campaign creation and state, schedules and settings, sequences, lead management, campaign analytics, email accounts and warmup, webhooks, block lists, domains, delivery diagnostics, and client controls. The normal order is: create or select a campaign, attach email accounts, configure sequences and a schedule, push an approved batch, then explicitly set campaign state. The current smartlead_push_to_campaign contract accepts up to 400 entries in lead_list; begin with a much smaller supervised pilot.
smartlead_update_campaign_status is the explicit state-change action; valid values include PAUSED, STOPPED, and START. Use a valid IANA timezone and 24-hour times when you set a schedule. Date-range analytics are limited by the live action contract, so inspect it before requesting a report. Recommended prompt:

Find the live contract when a workflow changes

Provider APIs change. Use the current contract before adding an action you have not used before:
For email discovery before activation, use Email waterfall. For Smartlead connection and provider-specific schemas, see the Smartlead provider guide.