Beta features
The brand features that unlock campaign tools, steps and triggers, and how a brand gets them.
Some campaign features are in beta. A brand has a feature when VYG has turned it on for that brand. Claude sees the same features as the VYG app: a tool, step or trigger your brand does not have is not offered, and a request that needs it is refused with the feature it needs and the options you do have.
To get a feature, ask your VYG account manager.
| Feature | What it unlocks |
|---|---|
beta:email-channel | The email step, the klaviyo_import, email_templates, email_broadcasts and manage_email_broadcast tools and the email.* stats keys. Separate from flow expansion. |
beta:flow-expansion | The Telegram, Resend email, outbound webhook, customer data update, discount, subscription, Klaviyo and branch condition steps. |
beta:whatsapp-node | The WhatsApp step, together with beta:flow-expansion. |
beta:nudge-node | The Nudge step: a follow-up in the conversation an earlier step of the campaign opened, sent from the agents' Nudge queue. Not on scheduled blasts. |
beta:canonical-triggers-armed | The checkout started, order shipped, customer replied and customer opted out triggers, together with beta:flow-expansion. |
beta:insight | Conversation insights: conversations action insights, find with insight_id, and the Insights screen. |
beta:flow-builder-variants | Reading message variants. Adding and changing variants is staff-only, as in the VYG app. |
beta:list-building | Sign-up forms (signup_forms, subscribe_signup_form). Changing forms (manage_signup_form) also needs update:workflows. |
The klaviyo_import and email_templates tools bring Klaviyo flows and templates into VYG and approve the
imported templates. They need you to sign in with your own VYG login. See Move from Klaviyo.
Reading, creating, changing, copying and turning on campaigns needs no beta feature, as in the VYG app. Turning a campaign on needs a plan that allows active campaigns (update:workflows). The wait, split, text, live agent and Slack steps and the checkout abandoned, order placed and subscription triggers are open to every brand.
Some brand settings hide campaigns rather than unlock them, the same way the VYG app does:
- Legacy (v1) workflows. A brand that has moved to the Campaigns builder (
beta:flow-v2-native) no longer sees its legacy workflows in the list, and reading one answers "not found". Turning onops:legacy-workflows-enabledfor the brand brings them back. Brands that have not moved see their legacy workflows next to their campaigns. - Scheduled blasts in shadow mode. While a brand's blasts are in shadow mode (
beta:blast-shadow-mode), they are left out of the list, the comparison and the run history, and opening or changing one is refused, as in the app.
Canonical triggers named like namespace.event (for example returns.requested) need beta:canonical-triggers-armed with flow expansion, and an enabled registration of that event for your brand. A trigger without an enabled registration is not offered.
Data sources (data_sources, manage_data_source) need no beta feature either: every brand can add and change them, as in the app.
Discounts (create_discount, update_discount) need the discount permission that comes with your plan
(update:discount_rules), the same rule as the discount form in the app. They need no beta feature.
campaigns view: "options" shows what your brand has:
node_cataloglists the step types it can use, each with the features it needs and, when a step needs setup first,unavailable_reason. See Campaign steps.trigger_eventslists the triggers it can use, the same list as the VYG app's trigger menu.message_variants.read_enabledandwrite_enabledsay whether you can read and change variants.