Route Tally form leads into Loops segments and Slack

When a new Tally form submission webhook fires (a demo request, waitlist signup, or contact form), classify the lead and route them into the right Loops nurture sequence with a Slack handoff for sales.

Trigger: incoming webhook from Tally for new form submissions.

Step 1 — Parse the submission. Pull email, first name, last name, role, company size, intended use case, and the free-text problem statement out of the Tally payload (see https://tally.so/help/webhooks for the field shape).

Step 2 — Drop blocklisted submissions. If the email domain matches a configurable blocklist of competitor or test/throwaway domains (start with example.com, test.com, mailinator.com, and our own domain), stop the workflow silently. Do not call Loops or Slack.

Step 3 — Classify the lead into one of these segments based on the submitted fields:

• self-serve-trial — solo users, small teams (under ~50 employees), or anyone just exploring.

• sales-led-demo — mid-market companies (roughly 50–500 employees) or anyone who explicitly asked to talk to sales.

• enterprise — large companies (500+ employees), procurement/security language, or enterprise-only requirements.

• not-a-fit — students, job seekers, vendors pitching us, or clearly off-topic submissions.

Step 4 — Look up the right mailing list in Loops. Call the List Mailing Lists operation in Loops and find the list id whose name matches the chosen segment (for example a list named "Self-serve onboarding", "Sales-led nurture", or "Enterprise nurture"). If the segment is not-a-fit, skip steps 5 and 6 entirely.

Step 5 — Create the contact in Loops. Call Create Contact with: email (required); firstName and lastName parsed from the Tally name field; source set to "tally-website"; the mailingLists object keyed with the matching segment list id set to true; and custom properties as top-level camelCase keys for role, companySize, useCase, and problemStatement. Loops stores any extra camelCase top-level key as a custom property automatically.

Step 6 — Fire the welcome event. Call Send Event in Loops with the email and a segment-specific event name: trial_signup for self-serve, sales_inquiry for sales-led, enterprise_inquiry for enterprise. This is what triggers each segment's published Loops workflow to send its welcome sequence.

Step 7 — Post a sales handoff to Slack. Use Send a Message in Slack Bot to post to the configured sales channel (default: #inbound-leads). Keep the message short and scannable. Include: the classification (as a label or emoji), the prospect's name and email, their role and company size, a one-line quote of their stated pain or use case, a recommended owner (AE for enterprise, SDR for sales-led, growth team for self-serve, no owner for not-a-fit), and a link back to the Tally response so anyone picking it up has full context.

Still post a brief note to Slack for not-a-fit submissions, but skip the Loops contact and event so they do not get added to any nurture sequence.