VYG Docs
Guides for brand teams

Campaign steps

The step types a campaign can have, the feature each needs, and which ones Claude can add or change.

A campaign is a trigger followed by steps. campaigns view: "options" returns this catalog for your brand as node_catalog, listing only the step types your brand can use. Each entry has:

  • type: the step type.
  • requires: the brand features it needs (none for the base steps). See Beta features.
  • unavailable_reason: present when the step needs setup first, with the same message the VYG app's add-step menu shows. Claude cannot add the step until it is set up.
  • ops: what Claude can do with it: add, update, remove. An empty list means the step is changed in the VYG app.
  • config_schema: the settings add_node and update_node take.
  • messages: for text, agent and Nudge steps, the text fields. Their text is not part of config.

Step types

StepTypeNeedsSet up firstClaude can
Waitwaitnothingadd, change, remove
Splitsplitnothingchange branch weights
Live agentagentnothingadd, change text, remove
Text (SMS)smsnothingInfobip connectedadd, change text, remove
Nudgenudgebeta:nudge-nodeadd, change, remove
SlackslacknothingSlack connectedVYG app only
Emailemailbeta:email-channela verified sending domainadd, change, remove
WhatsAppwhatsappbeta:flow-expansion, beta:whatsapp-nodeWhatsApp connected (Meta)add, change, remove
Telegramtelegrambeta:flow-expansionTelegram connectedadd, change, remove
Resend emailresendbeta:flow-expansionResend connectedadd, change, remove
Outbound webhookwebhook-outbeta:flow-expansionadd, change, remove
Customer data updatecdp-writebeta:flow-expansionthe CDP plan (list:cdp)add, change, remove
Discountdiscountbeta:flow-expansionShopify connectedVYG app only
Subscription actionsubscriptionbeta:flow-expansiona subscription app connectedVYG app only
Klaviyo listklaviyobeta:flow-expansionKlaviyo connectedVYG app only
Branch conditionbranchbeta:flow-expansionVYG app only

Text and live agent (SMS) steps send from a temporary number until your brand has its own texting number. campaigns view: "options" reports this in texting_setup, like the warning on those steps in the VYG app.

Audience sync, AI copy and AI classify steps are never offered. Scheduled blasts are not managed through the MCP.

Settings

Typeconfig
waitamount (1 to 999) and unit (minutes, hours, days).
splitbranches: one { name, weight } per existing branch, in order; weights add up to 100.
whatsapptemplate (name of an approved template, language, optional category), variables (template variable number to { source, fallback }), optional header (kind: none, image or document, and url).
telegramtext (up to 4,096 characters), variables (each ${namespace.field} in the text needs an entry with a fallback, keyed by the path with dots as underscores), optional button (label and url).
emailtemplate_id of a live email template of your brand (see email_templates), optional from_domain (one of your verified sending domains). Drafts and archived templates are refused.
resendtemplate_id, from, optional subject and variable_mappings (a JSON object string).
webhook-outurl: an https address. Requests are signed with your brand's webhook secret.
nudgeoptional quiet (amount and unit: hours or days): skip customers who messaged within it. 1 hour to 30 days, 48 hours when left out; null resets it to 48 hours. Optional discount_rule_id from your discount library (null removes it).
cdp-writeoperation (add_tag, remove_tag, set_property, emit_event) and the fields that operation uses: a tag, a property key and value, or an event type and properties. The exact keys are in config_schema.

Text, agent and Nudge steps take their text in messages: message for a text or Nudge step, initial_message and agent_reply_message for an agent step. The same message rules apply as for new campaigns. A message that uses ${generated.discount_code} needs a discount on its step.

Nudge steps

A Nudge step sends a follow-up in the conversation an earlier Live Agent or text step of the same campaign opened. The follow-up waits in the agents' Nudge queue, where an agent sends or skips it. It only goes to customers who replied to the first message, and it is skipped for customers who messaged within the quiet window or ordered since the conversation started. Put a wait before it to set when it goes out.

A Nudge step must come after a Live Agent (SMS) or text step on the same path; a wait in between is fine. add_node refuses a Nudge step with no such step before it, and remove_node refuses to remove the step a Nudge follows. Nudge steps are never offered on scheduled blasts.

update_node changes only the fields you pass; the rest keep their saved values.

Where a step goes

add_node inserts the new step after the step named in after, before whatever followed it. After a split, branch names the branch (its name or its 0-based index) and the step goes at the start of that branch.

Campaigns Claude cannot republish

When you change a campaign's steps, VYG updates the running campaign to match. Claude can do this for campaigns made only of the step types above other than Slack, Klaviyo and branch conditions. If a campaign has one of those, campaigns view: "get" returns graph.editable: false and a read_only_reason, and step changes are refused. Name, dates, filters, holdout, re-entry and message text can still be changed.

On this page