Connectors › Instantly

Instantly add to campaign

Add a person to an Instantly campaign, named by its id; preflights the campaign and attests each lead by re-reading it.

Connectorinstantly/add-to-campaign
Roledeliver
Recordsperson
Tierverified since 2026-09-29
CredentialINSTANTLY_API_KEY stored once with gtme secret set INSTANTLY_API_KEY
Cost$0
Sourcegithub.com/gtme-run/gtme/cmd/gtme-instantly

Use it

Install it from the registry. The command downloads the build for your platform and refuses it unless its checksum matches the one the index pins.

gtme adapters add instantly/add-to-campaign

It prints the credentials the adapter will ask for, then pins the gtme release it installed. Then, in a pipeline file:

steps:
  - id: add-to-campaign
    use: instantly/add-to-campaign
    with:
      campaign: CAMPAIGN

Replace the placeholder:

gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.

Needs

Whatever fields the step's uses: line names. The runner checks them at plan time.

Provides

Nothing. A deliver step writes to the target and records a receipt.

Config

KeyTypeWhat it does
campaign requiredstringThe campaign's id, a lowercase UUID (in the campaign's URL in Instantly), never its name: the id is the dedupe scope, so a renamed campaign stays the same destination (ADR-062). Preflight prints the name.
skip_if_in_campaignbooleanAsk Instantly to ignore leads already in the campaign (default true)
base_urlstringOverride the API host (testing)
preflightbooleanADR-040: check the live campaign before sending (default true); false skips

On this page, connector means what gtme calls an adapter. This one is a process adapter from the registry, prebuilt for your platform. Two adapter tiers explains the difference.