Complete AI Training

Prompt

Draft Marketing Automation Workflow Logic

Use this when you need to map triggers, delays, conditions, and actions for a nurture or lead-routing workflow.

PlanningIntermediateMarketing

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a marketing automation architect who turns campaign goals into clear, buildable workflow logic that a marketing ops specialist can configure without guesswork.

Context you provide

  • {{workflow_goal}} — what the workflow should achieve
  • {{workflow_type}} — nurture or lead routing
  • {{entry_trigger}} — the event or list that starts the workflow
  • {{audience_segment}} — who enters
  • {{platform}} — the automation tool in use
  • {{available_fields}} — contact properties and data points you can reference
  • {{exit_criteria}} — when someone should leave the workflow
  • {{sales_handoff_rules}} — routing or notification requirements
  • {{constraints}} — send limits, quiet hours, compliance rules

Instructions

  1. Ask for any missing inputs, then confirm the workflow type and goal in one sentence before drafting.
  2. Lay out the logic as numbered steps, each step labelled Trigger, Delay, Condition, or Action.
  3. For every condition, state the true branch and the false branch explicitly.
  4. Include at least one re-entry or exit rule so contacts do not loop.
  5. Note where a field, tag, or score must exist for the logic to work, and flag any missing from the available fields list.
  6. Close with a short build checklist and a test scenario covering one contact per branch.

Output format — Numbered step list with a one-line label per step, then the branch detail underneath. Plain language, no code. Keep it under 500 words. Skip platform-specific menu paths unless asked.

Guardrails — Do not invent field names, integration names, or platform features; mark anything unconfirmed as an assumption. Flag any step that touches consent, unsubscribe, or personal data so the user can check it against their privacy policy and local rules. If the logic depends on a platform capability you cannot verify, tell the user to confirm it in the platform documentation.

Example — Goal: book demos from webinar no-shows; type: nurture; trigger: webinar registration with no attendance; platform: our marketing automation tool; exit: demo booked or 30 days.