/run-sequence

name: run-sequence
description: Manage CRM sequences end-to-end — list, create, enroll contacts, activate/deactivate, duplicate, and track performance. Use when someone says "what sequences do I have", "create a welcome sequence", "enroll this contact in a sequence", "add these leads to my nurture sequence", "deactivate the cold outreach sequence", "activate my new sequence", "how is my nurture sequence doing", "show me sequence analytics", "create a drip campaign", "who is enrolled in", "duplicate this sequence", "set up a new outreach flow", "check this contact's sequence history", or "what sequences is this lead in".
argument-hint: "[optional: action + target — 'list sequences on Leads board', 'enroll Acme in welcome sequence', 'analytics for Q2 nurture', 'duplicate cold outreach']"
user-invocable: true
allowed-tools: [Read, AskUserQuestion, mcp__monday__get_user_context, mcp__monday__list_workspaces, mcp__monday__search, mcp__monday__get_board_info, mcp__monday__get_board_items_page, mcp__monday__get-board-sequences, mcp__monday__get-sequence-analytics, mcp__monday__get-contact-journey, mcp__monday__enroll-item-in-sequence, mcp__monday__activate-sequence, mcp__monday__deactivate-sequence, mcp__monday__duplicate-sequence, mcp__monday__create-sequence, mcp__monday__get-connected-email-accounts, mcp__monday__all_monday_api]

Run Sequence

Flow: **Trigger → Detect intent → Resolve board/sequence/contact → Execute → Confirm + report**.

Input

• Optional: action + target via argument (e.g., "enroll Acme in welcome sequence").
• If no argument: ask what they want to do.

Output

• **List:** sequences on a board with status, step count, enrollment counts, analytics.
• **Create:** new sequence scaffolded via the tool's built-in gate flow (board → steps → email sender if needed), starts INACTIVE.
• **Enroll:** one or more CRM items enrolled in a sequence; returns succeeded/failed counts.
• **Activate/Deactivate:** sequence state toggled with confirmation. Deactivate does NOT stop existing enrollments — only blocks new ones.
• **Duplicate:** copy of a sequence created in INACTIVE state.
• **Analyze:** per-run + level + step funnel (reply rate, open rate, click-through).
• **Contact journey:** all sequences a contact is enrolled in, sorted by most recent.

Knowledge

• Sequence states: ACTIVE (enrolling + running), INACTIVE (not enrolling; existing runs continue).
• `deactivate-sequence` ≠ pause — enrolled contacts keep progressing; only new enrollments are blocked.
• No sequence editing tool exists — steps cannot be added/modified via MCP. Direct users to Tools → Sequences in the UI.
• `get-board-sequences` requires a `board_id` — always resolve the board first.
• `create-sequence` has a built-in gate system: call it with what you have; if anything's missing the tool returns `CONFIRMATION_REQUIRED` with exact instructions — follow them verbatim, never pre-empt the gates.
• `enroll-item-in-sequence` takes `board_id`, `sequenceId`, and `itemIds` (array of string IDs).

Tools (MCP)

• `get-board-sequences` — list sequences on a board (needs `board_id`).
• `get-sequence-analytics` — per-run, level, and step analytics for one sequence.
• `get-contact-journey` — all sequences a contact/item is enrolled in (needs `board_id` + `item_id`).
• `enroll-item-in-sequence` — enroll one or more items in a sequence.
• `activate-sequence` — INACTIVE → ACTIVE.
• `deactivate-sequence` — ACTIVE → INACTIVE (existing enrollments continue).
• `duplicate-sequence` — copy a sequence; new copy starts INACTIVE.
• `create-sequence` — create a new sequence; call directly with whatever args you have.
• `get-connected-email-accounts` — list linked Gmail/Outlook accounts; used when `create-sequence` gate requires a sender.
• `get_user_context` — user identity + account.
• `search` / `get_board_info` / `get_board_items_page` — resolve boards and items by name.

Cross-skill handoffs

• **From daily-briefing:** brief can surface sequences with low engagement → suggest `/monday-crm:run-sequence analytics for <name>`.
• **From meeting-to-opportunity:** after logging a new lead, suggest enrolling them in an onboarding sequence.
• **To log-activity:** after enrolling a contact in a sequence whose first step is a manual call, suggest logging the call outcome.

---

Step 0: Connector check

1. Try `mcp__monday__get_user_context`. On error → print install prompt, stop. 2. This skill does not pre-check sequence tools — if a sequence tool fails with a permission error in later steps, print: *"Sequences may not be enabled on your account. Check Tools → Sequences in monday CRM."*

---

Step 1: Detect intent

Parse the argument/prompt to classify:

| Intent | Trigger signals | |---|---| | **list** | "what sequences", "show sequences", "list", no argument | | **create** | "create", "set up", "build", "new sequence", "drip campaign" | | **enroll** | "enroll", "add to sequence", "put in sequence", "start on sequence" | | **activate** | "activate", "turn on", "enable sequence" | | **deactivate** | "deactivate", "turn off", "disable sequence", "stop new enrollments" | | **duplicate** | "duplicate", "copy sequence", "clone" | | **analyze** | "analytics", "how is", "performance", "open rate", "funnel", "reply rate" | | **contact-journey** | "what sequences is", "sequence history for", "enrolled in", "contact journey" |

If ambiguous, ask once: > *"What would you like to do with sequences? (list / create / enroll / activate or deactivate / duplicate / analyze / check a contact's history)"*

---

Step 2: Resolve board

**Required for:** list, enroll, contact-journey. Optional for create (let the gate handle it).

1. If user named a board → `mcp__monday__search` or `get_board_info` to resolve it. On ambiguity, present top results and ask. 2. If no board named:

• For **list**: ask *"Which board's sequences do you want to see?"*
• For **create**: proceed to Step 4 and let the tool's gate request it.
• For **enroll*