Route to Campaign

Task type: Route to Campaign

Use Route to Campaign to choose the best live campaign for a contact from a campaign set.

Run behavior

• Side effects: This task is read-only or computation-only by default. It returns data for later steps rather than directly writing records or sending messages.
• Credit usage: This task is not classified as credit-billed by the workflow task registry.

When to use this task

• Route contacts into role-specific campaigns such as CEO, VP Sales, manager, or marketer tracks.
• Enroll contacts from a shared workflow when the exact campaign depends on title or account context.
• Use a fallback campaign when campaign fit is uncertain.

Setup tips

• Choose all live campaigns or provide a selected campaign list.
• Set a fallback campaign so uncertain matches still have a safe destination.
• Use this only after the user confirms enrollment side effects.

Examples

Route by role

Route a contact to the best persona-specific campaign after enrichment identifies their title.

Outputs

• Selected campaign id, native campaign id, confidence, fallback flag, rationale, and status.

Common pitfalls

• Using too many vague campaigns with similar names and descriptions.
• Leaving the fallback campaign empty.
• Expecting contacts already enrolled in every candidate campaign to be enrolled again.

Reference details

These details are generated from the workflow task registry and match the fields available in the builder.

Required fields

• contactId
• fallbackCampaignId

Variable-aware fields

Fields that accept variable references ({{ inputs.x }}, {{ steps.N.y }}) from the workflow's variable graph:

• contactId
• candidateCampaignIds
• fallbackCampaignId

Liquid template fields

Fields that are rendered through Liquid (variables plus filters and control flow):

• contactId
• candidateCampaignIds
• fallbackCampaignId

Builder guidance

When the Workflow Builder Genie configures this task, it follows this guidance:

Use when the user wants contacts routed across multiple live campaigns by role/persona fit. Require a fallback campaign and confirm side effects before enrolling.

Default configuration

New instances of this task start with the following configuration:

{
  "name": "Route to Campaign",
  "outputKey": "campaign_route",
  "taskType": "Route to Campaign",
  "description": "",
  "contactId": "{{inputs.contact_id}}",
  "candidateCampaignIds": [],
  "useAllLiveCampaigns": true,
  "fallbackCampaignId": ""
}