Segment Typeform NPS into MailerLite, alert detractors in Slack

By General Input

Every new NPS response lands in MailerLite with the right promoter, passive, or detractor group, and your CS team gets a same-day Slack ping for detractors.

Integrations

  • Typeform
  • MailerLite
  • Slack

Type

Deterministic Code

Categories

  • Marketing
  • Customer Support

Build a code workflow that routes every new Typeform NPS or feedback survey response into MailerLite with deterministic segmentation, and pings a Slack channel for any detractor.

Trigger: Typeform webhook. Use Typeform's Create or Update Webhook operation to register the workflow's incoming URL against the survey form, so the workflow runs whenever a new response is submitted.

From the webhook payload, extract three things: the respondent email, the NPS score (the numeric answer), and the free-text comment (the follow-up text answer). Also capture the response submitted_at timestamp as the survey date.

Step 1. Call MailerLite's Create or Update Subscriber with the email. Pass custom fields for nps_score, nps_comment, and survey_date. This upserts on email, so repeat respondents update in place instead of duplicating.

Step 2. Bucket the score deterministically: 9 or 10 is promoter, 7 or 8 is passive, 6 or below is detractor. Then call MailerLite's Assign Subscriber to Group with the matching group ID so downstream MailerLite automations (thank-you for promoters, win-back for detractors) fire correctly. The three group IDs should be configurable inputs on the workflow.

Step 3. If the bucket is detractor, call Slack's Send a Message into a customer success channel. The message should include the email, the score, and the verbatim comment, formatted clearly so a CSM can read it at a glance and reach out the same day. The Slack channel ID should also be a configurable input.

Promoters and passives should not produce a Slack message; they are handled entirely by the MailerLite automations attached to their group.

Keep the code path strictly deterministic: no LLM calls, no scoring agent. The score-to-bucket mapping, the field mapping, and the routing rule are all fixed logic.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsArchive Typeform job applications and screen every resumeMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in production