Follow-Up Pack — Transcript to Email (Template)

Turn a raw meeting transcript into a polished Follow-Up Pack (summary, decisions, action items, and a ready-to-send follow-up email). Built for consultants, operators, founders, sales calls, and customer success—anyone who wants consistent follow-through after meetings.

---

What this template does

When a transcript comes in, the workflow:

1. Normalizes the input payload (so different sources can work)
2. Uses an AI Agent to generate a structured Follow-Up Pack:
   • meeting summary
   • key decisions
   • action items (owners/dates when available)
   • a professional follow-up email draft
3. Formats the final email content
4. Sends the email via Resend (if enabled)
5. Returns a clean JSON response for testing and automation chaining

---

Nodes (high level)

• Webhook Trigger — intake point for transcript payloads
• Normalize Input (Code) — ensures stable input fields + supports test runs
• AI Agent (Follow-Up Pack Generator) — generates the follow-up pack + email draft
• Format Output (Code) — formats email subject/body and final response JSON
• Send Email (Resend via HTTP Request) — sends email when variables + recipient are provided

---

Webhook input format

Send a JSON body like this:

{ "transcript": "Jordan: Thanks for meeting today... (full transcript here)", "requester_name": "Jordan", "requester_email": "jordan@example.com", "meeting_title": "Acme Freight — Mobile App Issue Review", "meeting_date": "2026-02-22", "company": "Acme Freight", "tone": "professional" }

Minimum required field:

• transcript (everything else is optional)

---

Output format (Follow-Up Pack JSON)

Example response shape (fields may vary slightly depending on your configuration):

{ "status": "success", "follow_up_pack": { "meeting_title": "Acme Freight — Mobile App Issue Review", "summary": "Discussed the iOS login redirect loop impacting multiple users after the latest release...", "decisions": [ "Roll back the auth redirect change if workaround fails within 24 hours." ], "action_items": [ { "task": "Reproduce the login loop on iOS and identify the triggering redirect condition.", "owner": "Engineering", "due_date": "2026-02-23" }, { "task": "Send customer a workaround + ETA for a permanent fix.", "owner": "Support", "due_date": null } ], "email": { "subject": "Follow-Up: Acme Freight — Mobile App Issue Review", "body": "Hi Jordan,\n\nThanks again for today...\n\nSummary:\n...\n\nDecisions:\n...\n\nNext steps:\n...\n\nBest,\nFollow-Up Pack" } }, "metadata": { "processed_at": "2026-02-22T18:55:08.061Z", "test_mode": false } }

---

Testing (no email required)

You can test the workflow end-to-end without enabling email sending:

1. Run a test webhook payload containing transcript
2. Confirm the response includes:
   • summary
   • decisions
   • action items
   • email draft (subject + body)
3. Verify the JSON response returns cleanly

The email step is optional and can be gated so the template still runs if variables are not set.

---

Email sending (Resend) — workflow variables

To enable actual email sending, you'll need to set these workflow variables:

• RESEND_API_KEY — your Resend API key
• FROM_EMAIL — verified sender email in Resend
• FROM_NAME (optional) — display name, defaults to "Follow-Up Pack"
• REPLY_TO (optional) — reply-to address

Email will send only when:

• requester_email is provided, AND
• RESEND_API_KEY and FROM_EMAIL are set

---

Notes for reviewers

• This template is designed to be testable without external setup (webhook in → follow-up pack JSON out).
• Email sending via Resend is documented and can be enabled by setting workflow variables.
• Output is clean, automation-ready, and designed for real meeting follow-through.