Log Jotform NPS replies to Airtable and alert Slack on extremes

Build a deterministic code workflow that triages Jotform NPS and CSAT survey responses. No AI, no drafting. The value is the deterministic branch on the numeric score, the always-on Airtable audit trail, and a fast detractor alert in Slack.

Trigger: a Jotform webhook. The form I want to monitor posts to the workflow every time a customer submits an NPS or CSAT response. The webhook payload includes the submission ID and form ID.

Step 1: Use the Jotform Get Single Submission operation to pull the full submission by its ID. From the answers, extract the customer email, the numeric rating, the free-text comment, the form name, and the submission timestamp.

Step 2: Always write one row to Airtable using the Create Records operation. The target is a feedback table in a base I will pick at setup. Columns to populate: customer email, score, comment, form name, submission timestamp. This step runs for every response, before any branching, so the audit trail is complete.

Step 3: Branch on the numeric score. If the score is between 0 and 6 (detractor), use the Slack Bot Send a Message operation to post to my customer success escalation channel with the customer email and the full comment text so the CX team can reach out within the hour. If the score is 9 or 10 (promoter), use Send a Message to post to my marketing channel with the comment so the team can request a testimonial or review. If the score is 7 or 8 (passive), do nothing further. The Airtable row from Step 2 is the only record needed for passives.

Slack messages should include the form name, the score, the customer email, and the full comment, formatted clearly so a human can scan and act. Use the Slack Bot integration so the post comes from a shared bot identity rather than any individual user.

At setup, ask me for: the Jotform form ID (or let me pick from my forms), the Airtable base ID, the Airtable table name, the Slack channel for detractors, and the Slack channel for promoters. Keep the score cutoffs (0 to 6, 7 to 8, 9 to 10) configurable so I can tweak them later without rebuilding the workflow.