Skip to main content
Glama

Setup Outbound Campaign

setup_outbound_campaign
Destructive

Create a ready-to-use outbound email campaign in one flow: creates the campaign with its emails, assigns sender profiles, optionally imports contacts, marks it complete (not a draft), and optionally activates it. Pass emails, the emails in order: the user sees exactly those when approving the call. Use nodes and edges only for a branching (complex) sequence the user asked for. Ask for team, name, the email copy and sender profiles if not provided. When activate is true the campaign starts emailing enrolled contacts, so confirm that with the user first. Prefer this over create_campaign plus separate steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDays to send, e.g. ["monday", "tuesday", "wednesday", "thursday", "friday"]
nameYesCampaign name
edgesNoOnly with nodes: sequence edges connecting them
hoursNoSending hours in the schedule timezone, e.g. "09:00-17:00"
nodesNoOnly for a branching (complex) sequence; otherwise pass emails. Sequence nodes (startNode, emailNode, waitNode, etc.). Email nodes must use subject_a/body_a.
trackNoEnable open/click tracking
emailsNoThe emails in order (a simple sequence). Each follow-up waits wait_days after the previous email and, without its own subject, replies in the same thread.
team_idYesTeam UUID - get from list_teams
versionNoOnly with nodes: 3 = simple (linear), 2 = complex (branching; permanent). With emails it is always simple.
activateNoWhen true, activate campaign after setup (starts sending to enrolled contacts)
contactsNoOptional contacts to import after campaign creation (same shape as bulk_import_contacts)
timezoneNoSchedule timezone, e.g. America/Los_Angeles
category_idNoOptional campaign category/folder UUID
mark_completeNoWhen true (default), set is_draft false after setup if validation passes
include_catch_allNoInclude catch-all addresses (default true)
sender_profile_idsYesSender profile UUIDs to assign — get from list_sender_profiles
send_to_risk_levelsNoList Health levels to send to. Omit for SAFE/LOW/MEDIUM/HIGH default (Invalid off). null = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / edges / items / properties / sourceHandle / description
      Previous value: -"Branch handle for ifNode/switchNode outputs"New value: +"Branch handle for ifNode/switchNode outputs: \"true\" (yes) or \"false\" (no) for an ifNode, \"case_<id>\" for a switchNode case"
    • changedInput schema / properties / nodes / items / properties / data / description
      Previous value: -"Node settings. Email nodes use subject_a/body_a (and _b/_c/_d for A/B), wait, wait_unit."New value: +"Node settings. Email nodes use subject_a/body_a (and _b/_c/_d for A/B), wait, wait_unit. Other step types and their fields are listed in the update_campaign_sequence description and `supersend docs`."
    • changedInput schema / properties / nodes / items / properties / type / description
      Previous value: -"Node type: startNode, emailNode, waitNode, ifNode, switchNode, etc."New value: +"Node type: startNode, stopNode, emailNode, waitNode, ifNode, switchNode, httpApiRequestNode, moveToAnotherCampaignNode, taskNode, noteNode, or a linkedin*Node (profile visit, like, follow, comment, connection, connection with message, message, InMail, withdraw, wait until connected)"
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources