Your team lives in Slack. Your form responses don't.
Most form tools route submissions to an email inbox, a dashboard you check occasionally, or a spreadsheet that needs manual review. None of those are where fast-moving teams actually act on leads, support requests, or job applications. To send form submissions to Slack automatically, most people assume they need a developer or a paid Zapier plan. You need neither.
This tutorial covers the exact Make (Integromat) setup to route Promptly Forms submissions directly to a Slack channel in under 5 minutes — no code at any step.
Why Route Form Submissions to Slack
Most teams see a new form submission hours after it arrives. The response sits in an email inbox until someone checks it, or in a dashboard that nobody monitors unless reminded. For time-sensitive submissions — a new lead, a support escalation, a job application from a strong candidate — that lag has a real cost.
Routing form responses to Slack puts the notification where the team already is. A new lead appears in #sales the moment it's submitted. A support request lands in #support with all the context already visible. A job application shows in #hiring without anyone needing to log into a separate tool to find it. The 5-minute setup pays back every time a submission arrives.
What You Need Before Starting
- Promptly Forms account — free plan works; webhook access is included on all plans
- Make (Integromat) account — the free tier handles this setup comfortably
- Slack workspace — one where you can install apps and add bots to channels
- A form to connect — already built, or build one now at the AI form builder
How to Send Form Submissions to Slack: The 5-Minute Make Setup
This setup uses Make's webhook module to receive data from Promptly Forms and passes it to Slack. No code required at any point.
Step 1: Get your Promptly Forms webhook URL
Open your form in Promptly Forms and go to Settings → Integrations. You'll see a webhook section with a unique URL for that specific form — it looks like https://hook.promptlyforms.com/xxxxxxxx. Copy that URL. Each form has its own webhook endpoint, so if you plan to connect multiple forms to Slack, you'll create a separate Make scenario for each one. The Make integration page lists all available data fields your webhook will send.
Step 2: Create a new scenario in Make
Log into make.com and click Create a new scenario. When prompted to choose a trigger, search for Webhooks and select Custom Webhook. Click Add, give the webhook a name (something like "Promptly Contact Form"), and Make generates a listener URL. Copy that Make webhook URL and paste it into your Promptly Forms integration settings. Save both sides. Make is now listening for data from your form.
Step 3: Send a test submission
Open your form in a new browser tab and submit a test response with realistic data — real-looking name, email, and any other fields your form includes. Switch back to Make. The webhook module should display a green indicator and the payload it received. Click it to expand — you'll see all your form fields listed as variables. Make needs this initial submission to map the data structure. Without it, field variables won't appear in the next step.
Step 4: Add the Slack module
Click the + icon to add a module after the webhook trigger. Search for Slack and select Send a Message. Connect your Slack account when prompted — Make will request permission to post messages on your behalf. Once connected, choose the Slack channel where submissions should appear: #leads, #support, #general, or whichever channel fits your use case. Leave the message content open for now.
Step 5: Format your Slack message
In the message body, map your form field variables to a readable structure. Here's a format that works well for most lead and intake forms:
🔔 New Form Submission
*Name:* {{name}}
*Email:* {{email}}
*Company:* {{company}}
*Message:* {{message}}
*Submitted:* {{timestamp}}
Three formatting choices that make a real difference in a busy Slack channel: wrap field labels in *asterisks* to bold them, add one emoji at the top so the notification stands out visually, and always include the timestamp — team members need to know when the submission arrived, not just when they happened to see the notification. Map each {{variable}} by clicking into the field and selecting the corresponding value from your webhook data picker.
Step 6: Activate the scenario and confirm
Click the ON toggle in the top right of the Make scenario editor to activate it. Submit another test form. The Slack message should appear in your chosen channel within a few seconds. If it does, the setup is complete. If not, check the troubleshooting section below before assuming something is broken — the most common issues have simple fixes.
Send Form Submissions to Slack: Routing to Different Channels
A single-channel setup handles most use cases. But if you're running multiple form types — lead capture, support requests, job applications — routing each submission type to the right channel makes the notifications genuinely useful rather than just present.
Make's Router module splits your workflow into separate paths, each with its own filter and Slack module. Click the wrench icon on the connection between your webhook and Slack module, select Add a router, and Make inserts a routing node. Each path from the router can have its own filter condition. Path 1 might filter for submissions where the enquiry type field equals "sales" and route to #sales. Path 2 filters for "support" and routes to #support. Path 3 catches everything else with no filter and routes to a general channel.
You can also route by field value rather than form type. A budget dropdown above a specific threshold triggers a direct message to the sales manager. A submission with urgency set to "critical" sends to #support and also pings the on-call engineer directly. The filter conditions in Make use simple AND/OR logic — no code, just field names and values. The Make integration guide has the full filter reference if you need it.
Troubleshooting Common Issues
Webhook not receiving data. The most common cause is a scenario left in the OFF state — the toggle is in the top right of the scenario editor. An inactive scenario ignores all incoming data even if the webhook URL is correct. Activate the scenario and submit another test form.
Field variables showing as empty or missing. Make infers the data structure from the first submission it receives. If you added the Slack module before running a test submission, the field picker won't know what variables are available. Go back to the webhook module, run a test submission, then return to the Slack module — the variables will appear in the picker.
Slack authorisation failing. Go to Make → Connections in the left sidebar, find your Slack connection, and click Reconnect. Confirm that the Slack app has permission to post in the specific channel you chose — private channels require the bot to be added explicitly before it can post.
Messages not appearing in channel despite no errors. The Make Slack bot needs to be a member of the channel it's posting to. In Slack: right-click the channel name → Integrations → Add apps, then search for your Make connection and add it. Submit another test after adding the bot.
What to Build Next
With submissions routing to Slack, the most useful parallel step is connecting the same form to Google Sheets — so the team gets a real-time notification in Slack and every response accumulates in a spreadsheet for reporting and follow-up tracking. Both connections run through Make and can live in the same scenario as separate paths from a router.
If you want to filter Slack notifications — only alerting for high-priority or high-value submissions — add a Make filter condition on the Slack path. Lower-priority responses still go to Sheets; only flagged ones trigger the Slack message.
For more forms to connect, the Promptly Forms template library has lead capture, support, intake, and event registration forms — all compatible with the same Make and Slack setup. Build a new form in the AI form builder, grab the webhook URL, and add it to a new scenario.