sequence-builder

Sequence Builder Skill

Author sequence steps and their AI personalizations (p13ns) — the content side of outbound sequences.

Read before starting:

• tiga-gtm/docs/api-reference.md (Sequences API section)
• tiga-gtm/docs/merge-fields.md — important: email_body and linkedin_message are HTML fields; merge fields in them must use the <span class="tiga-merge"> format, not plain {{.FieldName}} syntax
• tiga-gtm/skills/sequence-builder/references/p13n-api.md for full p13n API detail and prompt-writing guidance

---

Key Concepts

Sequence must be inactive to modify steps. You cannot add, edit, or delete steps while a sequence is enabled. Always deactivate first, make changes, then reactivate.

Field casing differs by endpoint:

• Add-step requests use semantic snake_case fields such as step_name and step_instructions.
• PATCH requests accept snake_case or PascalCase aliases. Use snake_case consistently, always include action, and send only fields relevant to that action. SequenceEmail updates must include both email_subject and email_body.
• GET and create responses use the persisted step model and are mostly PascalCase. Do not copy an entire GET response into a PATCH request or mix its PascalCase fields with snake_case fields.

Step action types:

Action	Description	Content field
SequenceEmail	Automated email sent by the system	EmailSubject + EmailBody
LinkedInMessage	LinkedIn message sent via Chrome extension	LinkedInMessage
LinkedInConnect	LinkedIn connection request	(no content body)
UserTask	Manual task reminder shown to the rep (call, review, custom)	Instructions
PhoneCall	Phone call reminder for the rep	Instructions

P13n support: SequenceEmail and LinkedInMessage support AI personalization via merge fields. UserTask and PhoneCall do not — they show instructions to the rep, not outreach content.

What is a p13n? An AI-generated text snippet written fresh for each person the moment their outreach task is created. It is step-linked (attached via step_id), ephemeral (recomputed per person at task creation, not stored as a standing fact), and template-embedded (referenced in the step's content as {{.key}}).

P13Ns vs. Signals:

	P13N	Signal
Output	Outreach text (sentence, paragraph)	Fact or insight stored on person/account
Timing	Computed when task is created	Computed on demand or in batch
Stored where	Person's custom_columns (ephemeral per task)	Person's custom_columns (persistent)
Use case	Email opening, personalized hook, LinkedIn intro	Funding status, hiring signals, tech stack

Use a p13n when the output appears directly in email or LinkedIn content. Use a signal (signals skill) to store a fact for filtering, scoring, or routing.

How p13ns connect to steps:

1. Create a step (returns the step's ID)
2. Create a p13n with step_id = <step ID> (returns a key like personalized_opening_a1b2c3)
3. Update the step's email_body or linkedin_message to include {{.personalized_opening_a1b2c3}}
4. When a person is added to the sequence, the system auto-computes the p13n and substitutes the merge field

---

Workflow A: Create a New Personalized Step

Use when: Adding a new step to an existing sequence with AI-generated personalization.

Step 1: Find the target sequence

curl -X GET "https://app.tigalabs.com/api/v1/sequences" \
  -H "X-Tiga-Auth: $TIGA_API_KEY" \
  -H "Tiga-Pagination: {\"page\":1,\"page_size\":25,\"sort_by\":\"updated_at\",\"sort_order\":\"desc\"}"

Note the sequence ID and IsEnabled status.

Step 2: Deactivate the sequence (if active)

curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/deactivate" \
  -H "X-Tiga-Auth: $TIGA_API_KEY"

Step 3: Get the sequence description (find existing step IDs)

curl -X GET "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/description" \
  -H "X-Tiga-Auth: $TIGA_API_KEY"

Response is Markdown showing all steps with their UUIDs. Example:

## Steps (2)

1. **Send Email - Initial Outreach** (SequenceEmail) — immediately (weekdays only)
   ID: `step-uuid-1`

2. **LinkedIn Follow-up** (LinkedInMessage) — after 3 days (weekdays only)
   ID: `step-uuid-2`

Step 4: Add the step

To append after the last step, use the last step's UUID as stepToAppendToId. To insert as the first step, use the nil UUID 00000000-0000-0000-0000-000000000000.

curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/add-step?stepToAppendToId=<last-step-id>" \
  -H "X-Tiga-Auth: $TIGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "SequenceEmail",
    "step_name": "Initial Outreach",
    "email_subject": "Quick question about {{.AccountName}}",
    "email_body": "<p>Hi <span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.FirstName}}\" data-entity=\"Person\" data-alt-text=\"\">First Name</span>,</p><p>[PERSONALIZATION_PLACEHOLDER]</p><p>Would love to connect and share how we help teams like yours.</p><p>Best,<br><span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.UserName}}\" data-entity=\"User\" data-alt-text=\"\">User'\''s Name</span></p>",
    "can_run_on_weekends": false
  }'

email_body is HTML. Merge fields must use the <span class="tiga-merge"> format — see tiga-gtm/docs/merge-fields.md. Plain {{.FieldName}} text in an email body will appear as raw literal text in the editor and won't render as interactive merge field chips.

Response:

{
  "ID": "new-step-uuid",
  "Action": "SequenceEmail",
  "EmailSubject": "Quick question about {{.AccountName}}",
  "EmailBody": "..."
}

Save the ID — you need it to create the p13n.

After a successful create, show the user the newly created step:

See step here: https://app.tigalabs.com/app#/step/:ID/edit

(Use ID from the response.)

Step fields:

Field	Description
action	Required. See action types table above.
step_name	Display name for the step
email_subject	Email subject line (SequenceEmail only)
email_body	Email body HTML (SequenceEmail only) — merge fields must use <span class="tiga-merge"> format, not plain {{.FieldName}}
linkedin_message	LinkedIn message HTML (LinkedInMessage only) — same span format as email_body
step_instructions	Task or call instructions shown to the rep (UserTask, PhoneCall) — plain text, use {{.FieldName}} directly
requires_human_approval	If true, the rep must manually mark the task done before the sequence advances (UserTask, PhoneCall)
can_run_on_weekends	Whether the step can run on weekends (default: false)

Step 5: Create the P13N

curl -X POST "https://app.tigalabs.com/api/v1/p13n" \
  -H "X-Tiga-Auth: $TIGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "label": "Personalized Opening",
    "step_id": "<new-step-uuid>",
    "prompt": "Write a 2-sentence personalized opening for an email to {{.FirstName}}, {{.Title}} at {{.AccountName}}. Reference something specific from their LinkedIn headline: {{.PersonLi_Headline}}. Be conversational.",
    "word_limit": 60,
    "default_value": "I came across your profile and was impressed by your background.",
    "temperature": 0.6
  }'

Save the key from the response — e.g., personalized_opening_a1b2c3 — and the id. P13n prompts use plain {{.FieldName}} merge syntax. Full request-field table, response shape, and prompt-writing guidance: references/p13n-api.md.

Step 6: Update the step with the p13n merge field

Replace the placeholder in the email body with the p13n's <span class="tiga-merge"> element. Use the key, id, and computed_config.type from the p13n response.

curl -X PATCH "https://app.tigalabs.com/api/v1/step/<new-step-uuid>" \
  -H "X-Tiga-Auth: $TIGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "SequenceEmail",
    "email_subject": "Quick question about {{.AccountName}}",
    "email_body": "<p>Hi <span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.FirstName}}\" data-entity=\"Person\" data-alt-text=\"\">First Name</span>,</p><p><span class=\"tiga-merge\" data-custom-column-id=\"<p13n-id>\" data-computed-config-type=\"<computed_config.type>\" data-value=\"{{.personalized_opening_a1b2c3}}\" data-entity=\"AiSection\" data-alt-text=\"\">Personalized Opening</span></p><p>Would love to connect and share how we help teams like yours.</p><p>Best,<br><span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.UserName}}\" data-entity=\"User\" data-alt-text=\"\">User'\''s Name</span></p>"
  }'

Important: When updating a SequenceEmail step, always send both email_subject and email_body together. Use snake_case keys for all PATCH requests. Equivalent snake_case and PascalCase aliases are deduplicated, but conflicting values are rejected with a 400 response.

Step 7: (Optional) Preview the p13n on a sample person

# Start async run
curl -X POST "https://app.tigalabs.com/api/v1/p13n/<p13n-id>/run" \
  -H "X-Tiga-Auth: $TIGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "<a-real-person-uuid>"}'

# Poll until complete
curl -X GET "https://app.tigalabs.com/api/v1/p13n/<p13n-id>/run-status?person_id=<person-uuid>" \
  -H "X-Tiga-Auth: $TIGA_API_KEY"

Terminal statuses, polling cadence, and the by-email variant: references/p13n-api.md.

Step 8: Activate the sequence

curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/activate" \
  -H "X-Tiga-Auth: $TIGA_API_KEY"

---

Workflow B: Update Existing Step Content

Use when: The step already exists and you want to change its email body, subject, or LinkedIn message.

1. Get sequence description to find the step ID:

   curl -X GET "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/description" \
     -H "X-Tiga-Auth: $TIGA_API_KEY"
   

2. Deactivate the sequence:

   curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/deactivate" \
     -H "X-Tiga-Auth: $TIGA_API_KEY"
   

3. Read the current step content before patching — required for SequenceEmail steps where you need to preserve one of the two fields (subject or body):

   curl -X GET "https://app.tigalabs.com/api/v1/step/<step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY"
   

4. Update the step:

   For email steps (email_body is HTML — use <span class="tiga-merge"> for merge fields):

   curl -X PATCH "https://app.tigalabs.com/api/v1/step/<step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "SequenceEmail",
       "email_subject": "New subject line",
       "email_body": "<p>Hi <span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.FirstName}}\" data-entity=\"Person\" data-alt-text=\"\">First Name</span>, <span class=\"tiga-merge\" data-custom-column-id=\"<p13n-id>\" data-computed-config-type=\"<p13n-type>\" data-value=\"{{.my_p13n_key}}\" data-entity=\"AiSection\" data-alt-text=\"\">My P13n Label</span></p>"
     }'
   

   For LinkedIn steps (linkedin_message is also HTML — same span format):

   curl -X PATCH "https://app.tigalabs.com/api/v1/step/<step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "LinkedInMessage",
       "linkedin_message": "<p>Hi <span class=\"tiga-merge\" data-custom-column-id=\"null\" data-computed-config-type=\"null\" data-value=\"{{.FirstName}}\" data-entity=\"Person\" data-alt-text=\"\">First Name</span>, <span class=\"tiga-merge\" data-custom-column-id=\"<p13n-id>\" data-computed-config-type=\"<p13n-type>\" data-value=\"{{.my_p13n_key}}\" data-entity=\"AiSection\" data-alt-text=\"\">My P13n Label</span></p>"
     }'
   

   For task or call steps (instructions is plain text — use {{.FieldName}} directly):

   curl -X PATCH "https://app.tigalabs.com/api/v1/step/<step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "UserTask",
       "instructions": "Call {{.FirstName}} at {{.Phone}} to follow up on the email. Reference their role as {{.Title}} at {{.AccountName}}."
     }'
   

   curl -X PATCH "https://app.tigalabs.com/api/v1/step/<step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "PhoneCall",
       "instructions": "Call {{.FirstName}} — mention the email you sent and ask about their current outreach process."
     }'
   

5. Reactivate:

   curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/activate" \
     -H "X-Tiga-Auth: $TIGA_API_KEY"
   

Note: When you update a step's content, any p13n {{.key}} merge fields that no longer appear in the email body, email subject, LinkedIn message, or instructions are automatically deleted.

---

Workflow C: Add a Phone Call or Task Step

Use when: Adding a manual reminder step — a phone call prompt or a custom task for the rep. These are simpler than email/LinkedIn steps: no email body, no p13n.

1. Deactivate the sequence (Steps 1–3 from Workflow A)

2. Add the step:

   Phone call step:

   curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/add-step?stepToAppendToId=<last-step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "PhoneCall",
       "step_name": "Follow-up Call",
       "step_instructions": "Call {{.FirstName}} at {{.Phone}}. Reference the email you sent 3 days ago. Ask about their current outreach process.",
       "requires_human_approval": true,
       "can_run_on_weekends": false
     }'
   

   Custom task step:

   curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/add-step?stepToAppendToId=<last-step-id>" \
     -H "X-Tiga-Auth: $TIGA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "action": "UserTask",
       "step_name": "Research Before Call",
       "step_instructions": "Review {{.AccountName}}'s LinkedIn page and note any recent company news. Look for a relevant hook for the call.",
       "requires_human_approval": true,
       "can_run_on_weekends": false
     }'
   

   requires_human_approval: true means the rep must mark the task done before the sequence advances to the next step. Set to false if the step should auto-complete after the delay.

3. Activate the sequence:

   curl -X POST "https://app.tigalabs.com/api/v1/sequence/<sequence-id>/activate" \
     -H "X-Tiga-Auth: $TIGA_API_KEY"
   

---

Workflow D: Manage P13Ns Directly

List, inspect, update, or delete personalizations independently of step authoring:

• List all: GET /api/v1/p13ns (or ?step_id=<step-uuid> for one step's p13ns)
• Get one: GET /api/v1/p13n/<p13n-id>
• Update: PUT /api/v1/p13n/<p13n-id> — writable fields: label, prompt, word_limit, default_value, temperature
• Delete: DELETE /api/v1/p13n/<p13n-id>

Warning: If a deleted p13n is linked to a step, also remove its {{.key}} merge field from the step's content, otherwise the merge field renders as blank text.

Full payloads, preview-run polling, and prompt-writing guidance with examples: references/p13n-api.md.

---

Merge Fields

See tiga-gtm/docs/merge-fields.md for the full reference including entity types, display labels, and the common field list (Person, Account, LinkedIn, User, Dates).

Key rule: email_body and linkedin_message are HTML — merge fields in them require the <span class="tiga-merge"> HTML format. instructions (UserTask/PhoneCall) and AI prompt fields (p13n prompts, signal prompts) use plain {{.FieldName}} syntax.

Get the full list including custom columns: GET /api/v1/mergefields

---

Related skills: outreach to enroll people in the sequence and monitor performance; signals for persistent facts used in filtering/scoring; flow-builder for play_type: flow agent automations.