The gist
One-liner router that reads a company's connection-strength field and decides who drafts the outreach:
Specific— we have a relationship on file. Route the Zap to the partner who owns that relationship so the email comes from the right voice.Random— no relationship. Route to a random senior partner from the pool so the founder still hears from a real person, not a generic inbox.
Pairs with the intro / congrats outreach Zaps that fire when a new company deal lands — this snippet is the gate that picks who the email is actually from.
The flow
- Input —
inputData["connection strength"](string field from the CRM; bracket access because of the space in the key). - Empty check. Null, undefined, or whitespace-only →
Random. - Otherwise →
Specific. Downstream branches in the Zap key off this single field:Specificfans out into per-partner sub-branches (one per owning partner),Randompicks from a small pool of senior partners. - Return
{ result }. One field, two values, trivial to branch on.
Why this exists
The hardest part of outbound from a fund isn't writing the email — it's deciding who sends it. This snippet is the boring two-line decision that keeps the rest of the outreach automation honest: relationship in CRM, that partner sends; no relationship, the pool sends. No founder ever gets "hi, I'm an automation" as the From line.