mutual_introduction_email
Craft emails to connect two people in your network. Choose double opt-in for high-value introductions or direct for low-stakes connections, with a clear reason to connect.
Instructions
Write the email you send when you're connecting two people in your network — as the connector, not the person being introduced. Distinct from introduction_email (your reply when someone introduces you to a prospect). Common use: connecting a past client with a supplier, two founders who share a problem, a contact with a potential collaborator, or two clients who'd benefit from knowing each other. Two modes: double_opt_in (default — send to each person separately first, checking they're open to the intro before making it; standard best practice for high-value relationships and mutual respect) or direct (one email to both people at the same time; fine when you know both parties well and the introduction is low-stakes). For double_opt_in, use the target parameter to specify which person this individual email is addressed to. Required: person_a_name (first person being introduced), person_b_name (second person), reason_to_connect (why these two people should meet — be specific; 'they're both in tech' is weak, 'you're both solving the same cold-outreach problem from opposite angles' is strong). Optional: person_a_description (what Person A does — one line), person_b_description (what Person B does — one line), mode ('double_opt_in' | 'direct' — default double_opt_in), target (for double_opt_in only: 'a' or 'b' — which person this email is going to; default 'a'), your_name. Does not count against your monthly draft limit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| person_a_name | Yes | First name of the first person being introduced | |
| person_b_name | Yes | First name of the second person being introduced | |
| reason_to_connect | Yes | Why these two people should meet — be specific. 'They're both in marketing' is weak; 'you're both trying to solve the same client-onboarding problem from opposite sides' is strong. | |
| person_a_description | No | Optional: one-line description of what Person A does — e.g. 'runs a boutique UX studio', 'heads product at a Series A fintech'. Used to give context to Person B (or the opt-in request to Person A). | |
| person_b_description | No | Optional: one-line description of what Person B does — e.g. 'freelance brand strategist', 'co-founder of a B2B SaaS startup'. Used to give context to Person A (or the opt-in request to Person B). | |
| mode | No | double_opt_in (default): send to each person individually first, checking they want the intro before making it — best practice for high-value relationships. direct: one email addressed to both at the same time — fine when you know both well and the intro is low-stakes. | |
| target | No | For double_opt_in mode only: which person this email is going to — 'a' (asking Person A if they'd like to meet Person B) or 'b' (asking Person B if they'd like to meet Person A). Defaults to 'a'. Ignored in direct mode. | |
| your_name | No | Optional: your name for the sign-off |