Connect a form to Slack once and every response posts into the channel you choose, with the answers you picked laid out underneath. You authorize your own workspace, choose the channel, and the people who act on the response see it without opening Upform. It costs nothing on the free plan, which has no cap on responses.
To send a form to Slack with Upform, open the form's Connect panel, authorize Slack with your own workspace account, pick the channel the messages should land in, then choose which questions appear in the message. From the moment you publish, every submitted response posts one message. There is no message cap, no response cap and no paid tier standing in front of it: every integration ships on the free plan, next to unlimited forms, unlimited responses and all 21 question types.
1
Message per response
4
Steps to connect
∞
Responses, free plan
$0
Cost of the integration
How it works
No bot to build, no incoming-webhook URL to generate, no Zap in the middle taking a cut. The whole setup happens in the Connect panel of the form you already built.
Open the form, go to the Connect panel and choose Slack. Slack asks you to authorize Upform against your own workspace over OAuth. There is no bot token to paste and nothing to store in a shared password manager.
Choose the channel the messages should land in (#inbound-leads, #applications, #support), whichever one the right people already read. One form to one channel keeps the noise where it belongs.
A response can carry twenty answers and a channel does not need twenty lines. Pick the questions that make the message worth reading, and leave the long ones in the form builder for the response drawer.
Publish the form on its public link or as an embed. Every submitted response posts one message into the channel, in arrival order, for as long as the form is live.
Connect · Slack
SlackSlack workspace connectedConnectedThe result
One message per response, with the form it came from at the top and the answers you selected underneath. Readable on a phone, in the queue with everything else the team already watches.
#inbound-leads
New response · Enterprise demo request
Example message. You choose the lines, so a newsletter signup can post two and a discovery call can post ten.
What the message contains
The shape is the same every time, which is what lets somebody scan the channel at speed instead of reading it.
| Part of the message | What it carries | Example |
|---|---|---|
| Form name | Which form the response came from, so one channel can carry several forms without anyone guessing. | Enterprise demo request |
| Arrival time | The message posts on submit, so Slack's own timestamp is the time the response came in. | 9:41 AM |
| One line per question you picked | The question title, then the answer. Text, email, number, phone, date and address questions post plain values. | Work email · maya@northgate.io |
| Choice answers | The labels the person picked. A multiple choice question puts its selected labels on one line. | Design, Marketing |
| Rating and scale answers | The number behind the stars or the slider, so a 3 out of 10 is obvious at a glance. | 9 |
Questions that collect a document use file uploads, which are stored in Upform and scoped to the form that collected them. When you need to read a response properly rather than skim it, the responses table has search, a form filter, a date filter and CSV export, and a row opens a side drawer with every answer in order.
Use it with
A notification is only worth sending if somebody does something next. Two setups where posting the response into the right channel is the entire point.
A qualification form asks for company, team size and budget, and the answers land in the channel where the people who follow up already sit. The first person to see it replies in the thread and claims it, which beats an inbox rule nobody remembers writing.
Lead generation formsPost the name, the role applied for and the two screening answers into the hiring channel, and keep the CV and the cover letter in Upform. The team triages in Slack and only opens the response drawer for the people worth a real read.
Recruitment formsEach form carries a single Slack connection, so responses from a form go to one place. When two teams need two different channels, run two forms, or keep Slack for the team that triages and add a webhook for everything else. Conditional logic decides which questions a person sees (show, hide, jump and end form), not which channel the message goes to.
Beyond the channel
Slack is the fastest way to tell a person something happened. When the next step belongs to a system rather than a person, send the response somewhere it can be acted on programmatically, on the same free plan, on the same form.
Send the whole response as JSON to any endpoint you control, then decide what happens to it: route by answer, open a ticket, write to your own database, post into a second channel. A webhook fires on the same event as the Slack message, so you can run both on one form.
Form webhooksPoint Upform at an n8n webhook URL and build the rest of the flow visually: branch on an answer, enrich it, then post your own Slack message with exactly the formatting you want. Every request carries an HMAC-SHA256 X-Upform-Signature header, and you never hand over n8n credentials.
n8n form automation
Google SheetsAppends one row per response
NotionCreates a database row, with your field mapping
HubSpotCreates or updates the contact on submitEvery destination connects with your own account and runs on the free plan. The full list lives in the integrations directory.
Yes. The message is posted the moment the response is submitted, not on a digest and not when somebody remembers to check. If the channel is open on a screen while a person is filling the form in, the message arrives underneath the last one on its own. There is nothing to schedule and no refresh button to press.
Yes, and it is part of the setup rather than a setting you go hunting for. You pick which questions are included when you connect the form, so the channel gets the four answers that matter instead of all nineteen. Everything you leave out is still stored in Upform and still appears in the responses table, the side drawer and the CSV export.
Each form carries one Slack connection, so one form posts into one channel. You can repoint that connection at a different channel whenever you like. If two teams genuinely need the same responses in two places, add a custom webhook alongside Slack on the same form and fan the message out from there.
No. Every integration is included on the free plan, which is $0 forever and comes with unlimited forms, unlimited responses, all 21 question types and conditional logic. Pro is $12 a month and adds unlimited file storage, removes Upform branding and allows up to five team members. Online checkout is not live yet, so Pro accounts are set up manually and the team replies the same day.
Yours. The connection is per-user OAuth: you authorize Upform against your own Slack workspace, and it can only post where that account can already post. There is no shared bot token and no API key to paste anywhere. Disconnect it whenever you like and the form keeps collecting responses in Upform, the messages simply stop arriving.
A message is posted when a response is submitted, so somebody who opens the form and leaves half way through does not fill the channel with half-empty messages. They are still counted in Upform analytics as an incomplete, and the per-question drop-off funnel shows the exact question they stopped on. The channel stays readable and the diagnosis stays where it belongs.
Get started
Start with a template, connect your Slack workspace, and the right people see every response without opening another tab.
No credit card. Unlimited forms and responses on the free plan.