campaign-workflow

name	campaign-workflow
description	End-to-end campaign execution workflow for weather-triggered promotions

Campaign Workflow

When to Use

• User requests a campaign, promotion, or launch
• Multi-step coordination across agents is needed

Workflow Steps

1. Weather Validation -> Delegate to strategy agent

   • Strategy agent consults weather-analysis skill for thresholds
   • If weather doesn't trigger a promotion, report findings and stop

2. Segmentation -> Delegate to segmentation agent

   • Segmentation agent identifies target micro-segments using customer-segmentation skill

3. Creative Generation -> Delegate to content_generation agent

   • Content agent generates variants per segment using content-generation skill
   • Verify variant count matches the skill's rules

4. Approval -> request_approval tool (HITL gate)

   • Present plan summary to user
   • Include: campaign name, segments, variant count, projected revenue
   • Requires explicit human approval before proceeding

5. Launch -> queue_campaign with approvalToken from step 4

6. Channel Activation -> Execute ONCE immediately after launch:

   • send_pump_screen for fuel locations
   • send_app_push for mobile users
   • send_sms for messaging segments
   • These are one-time activations, NOT repeated on status queries

7. Performance Tracking -> Delegate to measurement agent

Day Queries (/day1, /day2, /day3)

These are STATUS QUERIES, not workflow triggers:

1. Call advance_campaign_time(campaignId, hours=24) to simulate that day
2. Call get_live_campaign_status(campaignId) or delegate to measurement agent
3. Report metrics and insights

Do NOT re-trigger channel delivery on day queries. Channels are activated ONCE at step 6 and remain active.

Approval Flow

• request_approval issues an approvalToken
• queue_campaign requires this token
• Never queue a campaign without an approved token