toflow-create-sequence

toflow — Create and Enroll a Sequence

This skill orchestrates toflow's sequence tools into one workflow: build the sequence, get it approved, then enroll people with correctly personalized (or AI-generated) content. The guide tools below are the live source of truth for schema, required fields, and node/edge structure — always call them before the matching mutating call, even if this skill summarizes the shape. This skill's own guidance covers what the guides don't own: message content quality and writing style, and the order to call things in.

Part 1 — Building the sequence

1. Call get_sequence_creation_guide (and get_sequence_schema for the full field/node-type reference) before calling create_sequence. These cover sequence-level scheduling config (timezone, send window, weekends, holidays), sending accounts, node types, field requirements, edge shape, and template variables. Node types include email, send_linkedin_connection, is_in_linkedin_network, linkedin_message, linkedin_inmail, whatsapp_message, and view_linkedin_profile — confirm the current full list via get_sequence_schema since it may expand. send_linkedin_connection and is_in_linkedin_network are the only branching node types (true/false edges, never a merge point); is_in_linkedin_network's true branch can't contain another conditional, and its false branch allows at most one send_linkedin_connection.
2. Before drafting account IDs into any node: call list_connected_accounts and get_account_load_stats, present accounts by label with their load stats, and let the user choose. Email nodes take a from_account_ids list (even for one account — never the singular from_account_id); LinkedIn/WhatsApp nodes take a single from_account_id. For every selected email account, confirm it has a signature configured before drafting any content — if not, stop and have the user set one via set_email_signature or in Settings first.
3. Call list_sequences and list_sequence_templates first — check whether an existing sequence or template already covers this campaign before building from scratch.
4. Never skip straight to create_sequence. Show the full plan (steps, channels, timing) and wait for explicit confirmation before creating it — treat a request like "make me a sequence for X" as the start of planning, not permission to create immediately.
5. See references/writing-and-scheduling-rules.md for message-writing quality (subject/body rules, tone, avoiding AI writing tells) and suggested step-to-step timing gaps — these are proposable defaults to confirm with the user, not enforced by the schema, so don't apply them silently.
6. If thread_emails is enabled, only the first email node gets an original subject — every later email node's subject must be Re: <first email's subject> since they land as replies in one thread.