overloop-cli

name	overloop-cli
description	Overloop CLI skill — manage prospects, campaigns, sourcings, and outreach via the Overloop API v2 from the terminal.

Overloop CLI Skill

Overloop is an AI-powered sales automation platform for managing prospects, campaigns, and outreach. This CLI lets you manage all resources from the terminal via the Overloop API v2.

Setup

npm install -g overloop-cli
overloop login
# Or set env var: export OVERLOOP_API_KEY=your_api_key

Concepts

• Prospect: A person you want to reach out to. Has email, name, custom fields, and can belong to an organization.
• Organization: A company a prospect belongs to.
• List: A group of prospects (tag-based).
• Campaign: An automated outreach sequence with steps (emails, delays, conditions, LinkedIn messages).
• Step: A single action in a campaign (email, delay, condition, LinkedIn visit/message, etc.).
• Enrollment: A prospect enrolled in a campaign.
• Sourcing: Automated prospect discovery from a 450M+ contact database using search criteria.
• Conversation: An email thread or LinkedIn conversation with a prospect.
• Exclusion List: Blocked emails and domains.
• Custom Field: User-defined fields on prospects/organizations.
• Sending Address: Connected email accounts used for sending.

All Commands

All output is JSON. Pipe to jq for filtering.

Auth

overloop login       # Interactive API key prompt
overloop logout      # Remove saved credentials

Prospects

overloop prospects:list [--page N] [--per-page N] [--sort field] [--search text] [--filter '{"key":"value"}'] [--expand relations] [--sourcing-id ID]
overloop prospects:get <id>                  # ID or email
overloop prospects:create --email [e-mail] [--first-name John] [--last-name Doe] [--organization-id ID]
overloop prospects:create --data '{"email":"[e-mail]","first_name":"John","last_name":"Doe"}'
overloop prospects:update <id> --first-name Jane
overloop prospects:update <id> --data '{"phone":"[phone]"}'
overloop prospects:delete <id>

Organizations

overloop organizations:list [--search text] [--filter '{"country":"US"}'] [--expand relations]
overloop organizations:get <id>
overloop organizations:create --name "Acme Corp" [--website https://acme.com]
overloop organizations:create --data '{"name":"Acme Corp","website":"https://acme.com"}'
overloop organizations:update <id> --name "New Name"
overloop organizations:delete <id>

Lists

Lists are also used as tags in campaign steps. To use the add_to_tags step type, create lists first and pass their IDs as tag_ids.

overloop lists:list [--search text]
overloop lists:get <id>
overloop lists:create --name "Hot Leads"
overloop lists:update <id> --name "Warm Leads"
overloop lists:delete <id>

Campaigns

Two sourcing patterns are supported:

Pattern A — Standalone sourcing as trigger: Create a sourcing separately, then reference it with --sourcing-id and --auto-enroll. The sourcing remains independent; the campaign only uses it as an enrollment trigger. campaign.sourcing_id is NOT set.

Pattern B — Embedded sourcing (preferred for new campaigns): Pass --search-criteria (and optionally --sourcing-limit) directly to campaigns:create. The API creates a sourcing owned by the campaign. Auto-enrollment is enabled automatically. campaign.sourcing_id IS set.

overloop campaigns:list [--filter '{"status":"on"}'] [--expand steps,sourcing]
overloop campaigns:get <id> [--expand steps]
overloop campaigns:create --name "Q1 Outreach" [--timezone "Etc/UTC"] [--sender-id ID]

# Pattern A: use existing standalone sourcing as trigger
overloop campaigns:create --name "Q1" --auto-enroll --sourcing-id <id>

# Pattern B: create embedded sourcing with the campaign (preferred)
overloop campaigns:create --name "Q1" --search-criteria '{"job_titles":["CTO"],"locations":[{"id":22,"name":"Belgium","type":"Country"}]}' --sourcing-limit 100

# Inline steps
overloop campaigns:create --data '{"name":"Q1","steps":[{"type":"delay","config":{"days_delay":5}},{"type":"email","config":{"subject":"Hi","content":"Hello"}}]}'

overloop campaigns:update <id> --status on
overloop campaigns:update <id> --auto-enroll --sourcing-id <id>   # Pattern A on update
overloop campaigns:update <id> --search-criteria '...'            # Pattern B on update
overloop campaigns:update <id> --no-auto-enroll                   # disable auto-enrollment
overloop campaigns:delete <id>
overloop campaigns:stats <id>                                    # performance metrics

Campaign Stats

campaigns:stats <id> returns comprehensive performance metrics:

• prospects: total, active, contacted counts
• enrollments: active, completed, exited, errored, waiting, scheduled, in_review, disenrolled
• email: sent, contacted, opened, clicked, replied, bounced, opted_out, open_rate, reply_rate, bounce_rate
• reply_sentiment: positive, neutral, negative
• linkedin: actions_performed, visited, messaged, invited, replied
• enrollment_sources: overloop_database, event_trigger, linkedin_extension, existing_prospects, csv_import

Rates are percentages (0-100). Metrics come from cached aggregation tables and may lag by a few minutes. Check last_updated_at for freshness.

Steps (campaign-scoped, require --campaign / -c)

Critical: step chaining. When creating steps individually (not inline via campaigns:create --data), you must chain each step to the previous one using --previous-step-id. Without it, steps are created as orphan root nodes and will not appear in the Overloop UI sequence editor. The recommended approach is to use inline steps with campaigns:create --data '{"steps":[...]}' which handles chaining automatically.

overloop steps:list --campaign <id>
overloop steps:get <step_id> --campaign <id>

# Individual step creation — MUST chain with --previous-step-id
STEP1=$(overloop steps:create --campaign <id> --type delay --config '{"days_delay":3}' | jq -r '.data.id')
STEP2=$(overloop steps:create --campaign <id> --type email --config '{"generate_with_ai":true}' --previous-step-id $STEP1 | jq -r '.data.id')
overloop steps:create --campaign <id> --type delay --config '{"days_delay":5}' --previous-step-id $STEP2

# Condition step — children use --position to select branch
overloop steps:create --campaign <id> --type condition --previous-step-id <id> --config '{"records_segment":{"filters":{}}}'
overloop steps:create --campaign <id> --type email --config '{"generate_with_ai":true}' --previous-step-id <condition_id> --position 0  # yes branch
overloop steps:create --campaign <id> --type linkedin_send_message --config '{"generate_with_ai":true}' --previous-step-id <condition_id> --position 1  # no branch

overloop steps:update <step_id> --campaign <id> --config '{"subject":"Updated"}'
overloop steps:delete <step_id> --campaign <id>

Step Config Reference

Do not include a signature in any email or LinkedIn message template. Overloop appends the sender's signature automatically.

Important: For linkedin_send_message and linkedin_send_invitation, always use message as the field name, not content. The content field is only for email steps. Using content on LinkedIn steps will result in messages appearing empty in the Overloop UI.

Core steps (most commonly used):

Step Type	Required Config	Example
delay	days_delay (int) and/or hours_delay (int). Min 10 minutes.	{"days_delay": 3}
email (AI)	generate_with_ai: true — AI writes subject+body using campaign pitch_settings	{"generate_with_ai": true}
email (manual)	subject + content (Liquid templates)	{"subject": "Hi {{ lead_firstname }}", "content": "Hello {{ lead_firstname }},\n\n..."}
linkedin_visit_profile	none	{}
linkedin_send_invitation	none (optional message, max 300 chars)	{"message": "Hi {{ lead_firstname }}, let's connect!"} or {}
linkedin_send_message (AI)	generate_with_ai: true or empty config (defaults to AI)	{"generate_with_ai": true} or {}
linkedin_send_message (manual)	message (Liquid template)	{"message": "Hi {{ lead_firstname }}, ..."}
linkedin_check_connection	none — branches: connected = yes (position 0), not connected = no (position 1)	{}
condition	records_segment with filters	{"records_segment": {"filters": {"groups": [...]}}}
email_and_linkedin_condition	none — branches based on whether prospect has LinkedIn	{}

Action steps:

Step Type	Required Config	Example
add_to_tags	tag_ids (array of list IDs — use lists:list to find IDs)	{"tag_ids": [123, 456]}
review	title (Liquid template)	{"title": "Review {{ lead_firstname }}"}
note	content (Liquid template)	{"content": "Contacted {{ lead_firstname }}"}
search_email	none	{}
assign_conversation	owner_id (user ID)	{"owner_id": 1547}
archive_conversation	none	{}
enroll_campaign	automation_id (campaign ID to enroll into). Optional: node_id, remove_from_original	{"automation_id": 42, "remove_from_original": true}
goto_step	node_id (step ID to jump to)	{"node_id": "uuid-of-step"}

Notification steps:

Step Type	Required Config	Example
notification_email	recipient_id (user ID), subject, content	{"recipient_id": 1547, "subject": "Alert", "content": "..."}
notification_sms	recipient_id, content	{"recipient_id": 1547, "content": "..."}
notification_in_app	recipient_id, content	{"recipient_id": 1547, "content": "..."}

Integration steps:

Step Type	Required Config	Example
salesforce	CRM-specific config	{}
hubspot	CRM-specific config	{}
pipedrive	CRM-specific config	{}
zoho	CRM-specific config	{}
slack	slack_id (channel), content	{"slack_id": "C12345", "content": "..."}

Branching (condition steps)

Condition steps create branches. Child steps use --position to specify which branch:

• --position 0 = yes branch (condition met)
• --position 1 = no branch (condition not met)

# Create a condition step
overloop steps:create --campaign <id> --type condition --config '{"records_segment":{"filters":{}}}'

# Add step on yes branch
overloop steps:create --campaign <id> --type email --config '{"generate_with_ai":true}' --previous-step-id <condition_id> --position 0

# Add step on no branch  
overloop steps:create --campaign <id> --type linkedin_send_message --config '{"generate_with_ai":true}' --previous-step-id <condition_id> --position 1

AI-Generated Content (generate_with_ai)

Supported on: email, linkedin_send_message, linkedin_send_invitation.

When generate_with_ai: true:

• Subject and content are generated at send time using the campaign's pitch_settings and message_personalization_settings.
• First outreach gets a unique cold message; follow-ups get contextual follow-up messages.
• You do NOT need to provide subject/content/message — they are generated automatically.
• Step-level message_personalization_settings can override campaign defaults (e.g. different language for a specific step).

For AI to work well, ensure campaign pitch_settings are filled (especially selling_description and campaign_intent).

Merge Tags (Liquid Templates)

Used in subject, content, and message fields for manual (non-AI) steps. Uses Liquid syntax.

Important: Always use | default: '' for prospect/organization fields to avoid blank output when data is missing.

Never include a signature in email or LinkedIn message templates. Overloop automatically appends the sender's signature (configured in Settings > Sending Addresses) to all outgoing messages. Adding a signature in the step content would result in a duplicate signature.

To get the full list of available merge tags dynamically (including custom fields for the account):

overloop merge-tags:list                          # all tags
overloop merge-tags:list --group prospect         # only prospect tags
overloop merge-tags:list --group custom_field     # only custom field tags

Prospect (prefer prospect_ prefix over lead_ — both work):

Tag	Description
{{ prospect_firstname | default: '' }}	First name
{{ prospect_lastname | default: '' }}	Last name
{{ prospect_name | default: '' }}	Full name
{{ prospect_email | default: '' }}	Email address
{{ prospect_jobtitle | default: '' }}	Job title
{{ prospect_title | default: '' }}	Title (Mr, Mrs, etc.)
{{ prospect_phone | default: '' }}	Phone number
{{ prospect_company_name | default: '' }}	Organization name
{{ prospect_linkedin_profile | default: '' }}	LinkedIn profile URL
{{ prospect_country | default: '' }}	Country
{{ prospect_city | default: '' }}	City
{{ prospect_state | default: '' }}	State/region
{{ prospect_industry | default: '' }}	Industry

Organization:

Tag	Description
{{ organization_name | default: '' }}	Organization name
{{ organization_website | default: '' }}	Website
{{ organization_country | default: '' }}	Country
{{ organization_city | default: '' }}	City
{{ organization_phone | default: '' }}	Phone

Sender (campaign sender — no default needed, always set):

Tag	Description
{{ sender_name }}	Sender's full name
{{ sender_firstname }}	Sender's first name
{{ sender_lastname }}	Sender's last name
{{ sender_email }}	Sender's email
{{ sender_phone }}	Sender's phone
{{ sender_company_name }}	Sender's company name

Owner (prospect owner): {{ owner_name }}, {{ owner_firstname }}, {{ owner_lastname }}, {{ owner_email }}, {{ owner_phone }}

Company (your account): {{ company_name }}, {{ company_website }}, {{ company_phone }}

Campaign & threading:

Tag	Description
{{ automation_name }}	Current campaign name
{{ thread_subject }}	Previous email subject (for follow-ups: Re: {{ thread_subject }})

Conditions (for conditional content with {% if %}...{% endif %}): is_monday, is_tuesday, is_wednesday, is_thursday, is_friday, is_saturday, is_weekday, is_weekend

Example: {% if is_monday %}Happy Monday!{% endif %}

Custom fields: {{ prospect_c_<field_code> | default: '' }}, {{ organization_c_<field_code> | default: '' }}

Use overloop merge-tags:list --group custom_field or overloop custom-fields:list to discover available codes.

Enrollments (campaign-scoped, require --campaign / -c)

overloop enrollments:list --campaign <id>
overloop enrollments:get <enrollment_id> --campaign <id>
overloop enrollments:create --campaign <id> --prospect <prospect_id>
overloop enrollments:create --campaign <id> --prospect <prospect_id> --reenroll --start-at "2026-04-01T09:00:00Z"
overloop enrollments:bulk --campaign <id> --prospects "id1,id2,id3"       # bulk enroll up to 100
overloop enrollments:delete <enrollment_id> --campaign <id>

Step Types

overloop step-types:list     # List all available step types

Sourcings

Required fields for create: --name, --search-criteria, --sourcing-limit (max prospects to source).

Naming: Use only ASCII characters in names — avoid em dashes (—), curly quotes, or other special Unicode characters that can break shell escaping.

overloop sourcings:list
overloop sourcings:get <id>
overloop sourcings:create --name "Sales Belgium" --sourcing-limit 100 --search-criteria '{"job_titles":["sales"],"locations":[{"id":22,"name":"Belgium","type":"Country"}],"company_sizes":["1-10 employees"]}'
overloop sourcings:update <id> --name "Updated" --sourcing-limit 200
overloop sourcings:delete <id>
overloop sourcings:start <id>
overloop sourcings:pause <id>
overloop sourcings:clone <id>

Estimate Prospect Match Count

Preview how many prospects match search criteria before creating a sourcing (no credits consumed):

overloop sourcings:estimate --search-criteria '{"job_titles":["CEO"],"locations":[{"id":22,"name":"Belgium","type":"Country"}],"company_sizes":["1-10 employees"]}'
# Returns: { estimated_count: 2450, estimated_count_after_rejection: 1837, preview: [...] }

Use this to validate criteria and avoid wasted iterations. The preview array contains up to 5 sample prospect profiles.

Sourcing Search Options

Important: locations and industries must be objects (not plain strings). Use search-options to find valid values with their IDs.

Discover available values for sourcing search criteria fields:

overloop sourcings:search-options                             # All fields
overloop sourcings:search-options --field locations            # Location options
overloop sourcings:search-options --field locations --q "Bel"  # Search locations
overloop sourcings:search-options --field industries
overloop sourcings:search-options --field company_size
overloop sourcings:search-options --field management_level
overloop sourcings:search-options --field department
overloop sourcings:search-options --field technologies --q "React"

Conversations

overloop conversations:list [--archived]
overloop conversations:get <id>
overloop conversations:update <id> --name "New Subject"
overloop conversations:archive <id>
overloop conversations:unarchive <id>
overloop conversations:assign <id> --owner <user_id>

Account & Users

overloop account:get          # Account details
overloop me                   # Current authenticated user
overloop users:list
overloop users:get <id>

Merge Tags

overloop merge-tags:list                          # all available merge tags
overloop merge-tags:list --group prospect         # filter by group
overloop merge-tags:list --group custom_field     # custom fields for the account

Groups: prospect, organization, sender, owner, company, campaign, thread, condition, custom_field.

Custom Fields

overloop custom-fields:list
overloop custom-fields:list --type prospects

Sending Addresses

overloop sending-addresses:list

Exclusion List

overloop exclusion-list:list [--search text] [--filter '{"item_type":"domain"}']
overloop exclusion-list:create --value [e-mail] --item-type email
overloop exclusion-list:create --value baddomain.com --item-type domain
overloop exclusion-list:delete <id>

search_criteria Format Reference

Locations — MUST be objects

Locations must be objects with id, name, and type fields. Plain strings silently match nothing.

Correct: {"id": 22, "name": "Belgium", "type": "Country"}
Wrong:   "Belgium"                    ← silently matches nothing
Wrong:   {"name": "Belgium"}          ← missing id and type, rejected

Valid type values: Region, Country, State, City.

Always look up locations first:

overloop sourcings:search-options --field locations --q "Belgium"
# Returns: [{"id": 22, "name": "Belgium", "type": "Country"}, {"id": 1376, "name": "Brussels-Capital Region", "type": "State"}, ...]

Industries — MUST use API names, not LinkedIn names

Industries must be objects with id and name. The API uses its own industry names, which differ from LinkedIn names.

Correct: {"id": 575, "name": "Information Technology"}
Wrong:   "Information Technology and Services"    ← LinkedIn name, matches nothing
Wrong:   {"name": "Information Technology"}       ← missing id, rejected

Important: Industry names in the API differ from LinkedIn names (e.g. LinkedIn's "Information Technology and Services" is "Information Technology" in the API). Never guess — always look up the correct name and ID first:

overloop sourcings:search-options --field industries --q "Information"
# Returns: [{"id": 575, "name": "Information Technology", "alternates": ["Information Technology and Services"]}, ...]

Other search_criteria fields

Field	Format	Lookup
job_titles	["CEO", "CTO"] (free text)	No lookup needed
company_sizes	["1-10 employees"]	search-options --field company_sizes
management_level	["C-Level", "Director"]	search-options --field management_levels
departments	["Sales", "Marketing"]	search-options --field departments
prospect_keywords	["saas", "ai"] (free text)	No lookup needed
technologies	["React", "Python"]	search-options --field technologies

Message Personalization Settings

When creating or updating campaigns, you can set message_personalization_settings and pitch_settings to control AI-generated messages.

message_personalization_settings

Field	Accepted values	Default
language	english (United States), english (United Kingdom), french, spanish, german, dutch, portuguese (Brazil), portuguese (Portugal), danish, finnish, swedish, italian, norwegian, romanian, hebrew, turkish, polish	english (United States)
formality	formal, friendly, neutral	friendly
tone_of_voice	confident, persuasive, witty, straightforward, empathetic	persuasive
length	short, medium, long	short

pitch_settings

Field	Description
website_url	Your company website
selling_description	What you sell / your value proposition
pain_points	Problems your product solves
benefits	Key benefits for the prospect
proof_points	Social proof, case studies, numbers
campaign_intent	What you want from the prospect (e.g. "Book a demo")

Complete campaign creation example

A single --data call that creates a fully configured campaign with AI steps, pitch settings, and personalization:

overloop campaigns:create --data '{
  "name": "Acme // FR // CMOs // EN // v1-growth",
  "sender_id": 1547,
  "timezone": "Europe/Brussels",
  "sending_days": ["monday","tuesday","wednesday","thursday","friday"],
  "start_sending_minutes": 540,
  "end_sending_minutes": 1020,
  "pitch_settings": {
    "website_url": "https://acme.com",
    "selling_description": "Acme provides growth analytics for B2B SaaS companies.",
    "pain_points": "- No visibility on pipeline velocity\n- Manual reporting wastes 10h/week",
    "benefits": "- Real-time pipeline dashboard\n- AI-powered forecasting\n- Integrates with your CRM in 5 min",
    "proof_points": "- 200+ B2B SaaS clients\n- 35% faster deal cycles on average",
    "campaign_intent": "Book a 15-min demo"
  },
  "message_personalization_settings": {
    "language": "english (United States)",
    "formality": "friendly",
    "tone_of_voice": "straightforward",
    "length": "short"
  },
  "steps": [
    {"type": "linkedin_visit_profile", "config": {}},
    {"type": "delay", "config": {"hours_delay": 12}},
    {"type": "linkedin_send_invitation", "config": {"generate_with_ai": true}},
    {"type": "delay", "config": {"days_delay": 3}},
    {"type": "email", "config": {"generate_with_ai": true}},
    {"type": "delay", "config": {"days_delay": 5}},
    {"type": "linkedin_send_message", "config": {"generate_with_ai": true}},
    {"type": "delay", "config": {"days_delay": 10}},
    {"type": "email", "config": {"generate_with_ai": true}}
  ]
}'

This creates a 9-step LinkedIn + email sequence where AI generates all messaging using the provided pitch context. The campaign is created in off status — activate with campaigns:update <id> --status on after enrolling prospects or linking a sourcing.

Common Workflows

Pattern B (preferred): embedded sourcing campaign

Use this when creating a new campaign that should source its own prospects. Prefer inline steps in campaigns:create --data to avoid step chaining issues.

# 1. Look up location and industry IDs
overloop sourcings:search-options --field locations --q "Belgium"
overloop sourcings:search-options --field industries --q "Software"

# 2. Estimate match count (no credits consumed)
overloop sourcings:estimate --search-criteria '{"job_titles":["CTO","VP Engineering"],"locations":[{"id":22,"name":"Belgium","type":"Country"}],"industries":[{"id":4,"name":"Software Development"}],"company_sizes":["11-50 employees","51-200 employees"]}'

# 3. Create campaign with embedded sourcing AND inline steps (preferred — chaining is automatic)
overloop campaigns:create --data '{
  "name": "Q1 Tech Outreach",
  "timezone": "Europe/Brussels",
  "search_criteria": {"job_titles":["CTO","VP Engineering"],"locations":[{"id":22,"name":"Belgium","type":"Country"}],"industries":[{"id":4,"name":"Software Development"}],"company_sizes":["11-50 employees","51-200 employees"]},
  "sourcing_limit": 200,
  "steps": [
    {"type": "delay", "config": {"days_delay": 2}},
    {"type": "email", "config": {"generate_with_ai": true}},
    {"type": "delay", "config": {"days_delay": 3}},
    {"type": "email", "config": {"generate_with_ai": true}}
  ]
}'

# 4. Start the embedded sourcing (get sourcing_id from the campaign response)
overloop sourcings:start <sourcing_id>

# 5. Activate the campaign
overloop campaigns:update <campaign_id> --status on

Pattern A: standalone sourcing as trigger

Use this when you have an existing sourcing you want to wire as an enrollment trigger for a campaign. Prefer inline steps to avoid step chaining issues.

# 1. Create a standalone sourcing
overloop sourcings:create --name "Belgian Tech CTOs" --search-criteria '{"job_titles":["CTO"],"locations":[{"id":22,"name":"Belgium","type":"Country"}]}' --sourcing-limit 200

# 2. Create campaign with sourcing trigger AND inline steps
overloop campaigns:create --data '{
  "name": "Q1 Tech Outreach",
  "timezone": "Europe/Brussels",
  "only_allow_manual_enrollment": false,
  "sourcing_id": "<sourcing_id>",
  "steps": [
    {"type": "delay", "config": {"days_delay": 1}},
    {"type": "email", "config": {"generate_with_ai": true}},
    {"type": "delay", "config": {"days_delay": 3}},
    {"type": "email", "config": {"generate_with_ai": true}}
  ]
}'

# 3. Start sourcing, activate campaign
overloop sourcings:start <sourcing_id>
overloop campaigns:update <campaign_id> --status on

Manual enrollment flow

Prefer inline steps with campaigns:create --data for reliable step ordering:

# 1. Create campaign with inline steps
overloop campaigns:create --data '{
  "name": "Q1 Cold Outreach",
  "timezone": "Europe/Brussels",
  "steps": [
    {"type": "delay", "config": {"days_delay": 1}},
    {"type": "email", "config": {"subject": "Quick question", "content": "Hi {{first_name}},\n\nWould love to chat about...\n\nBest"}}
  ]
}'

# 2. Enroll prospects (single or bulk)
overloop enrollments:create --campaign <campaign_id> --prospect <prospect_id>
overloop enrollments:bulk --campaign <campaign_id> --prospects "id1,id2,id3"

# 3. Activate
overloop campaigns:update <campaign_id> --status on

List prospects from a sourcing

overloop prospects:list --sourcing-id <sourcing-uuid>
overloop prospects:list --sourcing-id <sourcing-uuid> --per-page 1000   # get up to 1000

Export prospect data

overloop prospects:list --per-page 1000 | jq '.data[] | {email, first_name, last_name, company: .organization_name}'
overloop prospects:list --sourcing-id <id> --per-page 1000 | jq '.data[] | {email, first_name, last_name}'

Pre-Launch Checklist

Before activating a campaign with campaigns:update <id> --status on, verify ALL of the following. Campaigns that fail these checks will silently do nothing.

# 1. At least one sending address connected?
overloop sending-addresses:list
# MUST return at least 1 address. If empty, the user needs to connect an email account in the Overloop UI.

# 2. Campaign has messaging steps?
overloop campaigns:get <id> --expand steps
# MUST have at least 1 email or linkedin step. A campaign with only delays does nothing.

# 3. Prospects will enter the campaign?
# Option A: manual enrollment — at least 1 prospect enrolled
overloop enrollments:list --campaign <id>
# Option B: auto-enrollment — sourcing_id is set and sourcing is active
overloop campaigns:get <id>
# Check: only_allow_manual_enrollment = false AND sourcing_id is present

# 4. Pitch settings filled? (only if steps use generate_with_ai)
overloop campaigns:get <id>
# Check: pitch_settings.selling_description is not empty.
# If empty, update: overloop campaigns:update <id> --data '{"pitch_settings":{"selling_description":"...","campaign_intent":"..."}}'

If a check fails:

Check	Fix
No sending address	User must connect one in Overloop UI (Settings > Sending Addresses)
No messaging steps	Add steps using inline creation or chain with --previous-step-id (see Steps section)
No prospects enrolled	Enroll: overloop enrollments:create --campaign <id> --prospect <id> or link a sourcing
Empty pitch_settings	Update: overloop campaigns:update <id> --data '{"pitch_settings":{...}}'

Error Handling

• Exit code 0: Success. Output is JSON on stdout.
• Exit code 1: Error. Message is printed to stderr.
• 401: Invalid or missing API key.
• 403: Insufficient permissions or account restrictions.
• 404: Resource not found.
• 422: Validation error (see common errors below).
• 429: Rate limited (600 requests/minute per key).

Error response format:

{"error": {"type": "validation_error", "message": "Validation failed: Enter triggers can't be blank"}}

Common Errors and Recovery

"Enter triggers can't be blank"

• Cause: Setting only_allow_manual_enrollment: false without a sourcing.
• Fix: Use --auto-enroll --sourcing-id <id> or --search-criteria '...' to provide a sourcing. Never set only_allow_manual_enrollment: false without one.

"Auto-enrollment requires a sourcing_id or search_criteria"

• Cause: --auto-enroll flag without --sourcing-id or --search-criteria.
• Fix: Create a sourcing first (sourcings:create), then pass --sourcing-id, or use --search-criteria for embedded sourcing.

"Validation failed" on search_criteria

• Cause: Locations passed as strings instead of objects, or invalid industry names.
• Fix: Always use sourcings:search-options to look up correct {id, name, type} objects before creating sourcings.

"sourcing_limit: can't be blank"

• Cause: sourcings:create without --sourcing-limit.
• Fix: Always pass --sourcing-limit <number> when creating a sourcing.

Campaign activated but not sending messages

• Cause: No sending address connected, or no prospects enrolled, or no messaging steps.
• Fix: Run the pre-launch checklist above. Check sending-addresses:list, verify steps exist, and confirm prospects are enrolled or sourcing is active.

"Timezone can't be blank"

• Cause: Creating a campaign without a timezone (only happens with --data if timezone is omitted).
• Fix: Include "timezone": "Etc/UTC" in the payload, or use --timezone. The CLI defaults to Etc/UTC when using flags.

Environment Variables

Variable	Required	Description
OVERLOOP_API_KEY	No	API key (overrides saved config from overloop login)
OVERLOOP_API_URL	No	Override base URL (default: https://api.overloop.ai)