Post new job applications to your hiring channel
Applications land in a private #hiring channel with the role and the candidate's skills, and reviewers thread their notes under each one.
New submission on your "Careers application" form
Send a channel message to #hiring with the role, the candidate's name and their experience
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring goes quiet between the job ad and the shortlist, usually because the applications sit in a tool only one person opens. Posting each one into #hiring puts the role, the name and the candidate's own account of their skills in front of everyone doing the screening, on the day it arrives.
Recruiters and hiring managers then work in the thread under each message — one place for the read, the argument and the decision. Keep the channel private and limited to reviewers; an application is personal data, and a Slack channel keeps everything ever posted in it.
Setting it up
- 1
Create the private #hiring channel before you build anything and add only the people who will screen. Invite the Zapier app with /invite, or the channel will not appear in the action step.
- 2
Publish the job application form and keep Position Applied For as a fixed list of open roles, so messages can be filtered and searched by role later on.
- 3
In Zapier, set the New Submission trigger to watch the application form, then run one complete test application so the sample carries the long answers as well as the short ones.
- 4
Add Slack's Send Channel Message action, connect the workspace, and choose the private #hiring channel as the destination.
- 5
Open the message with Position Applied For rather than the name. Reviewers screen role by role, so the role belongs on the first line and Full Name underneath it.
- 6
Add Available Start Date and Highest Level of Education to the same block, and leave City, State out unless location genuinely changes who can do the job.
- 7
Map Relevant Skills as the body and stop there. Work Experience and Cover Letter stay in your responses list, where they are easier to read at length than in a chat window.
- 8
Agree a reaction convention with reviewers, tell them to leave notes in the thread rather than the channel, then switch the Zap on.
What maps where
Using the Job Application Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Slack |
|---|---|
| Position Applied For | First line of the message, above the candidate's name |
| Full Name | Second line, on its own |
| Available Start Date | Third line, beside the education answer |
| Highest Level of Education | Third line, for roles with a formal requirement |
| Relevant Skills | Body of the message |
| How Did You Hear About This Position? | Final line, so you can see which channel is working |
Variations worth knowing
Use Zapier paths on Position Applied For and send each role to its own private channel. Reviewers then only see the roles they are screening, and a channel for a closed role can be archived with its whole history intact.
Put Digest by Zapier between the trigger and the Slack step and release it each morning. #hiring gets a single message listing the day's applicants, which suits a role that draws thirty applications a week rather than three.
If something isn't arriving
Slack permissions are set per channel, and anyone added to #hiring later can scroll back through every application already posted. Keep it private, review the member list at the start of each round, and never post candidates into a channel contractors can join.
Slack stops a message at a few thousand characters, which a full work history clears on its own. Leave the long answers out of the template and map only the skills line; reviewers open the complete application in formformform when they sit down to shortlist.
Frequently asked questions
Is it safe to post job applications into Slack?
Keep the channel private and limited to the people screening. Responses in formformform are encrypted at rest and in transit, with EU hosting available, but anything copied into a Slack message is then governed by your workspace's own retention settings.
Can I stop applications posting once a role is closed?
Turn that Zap off, or add a filter on Position Applied For so closed roles are skipped. Submissions still arrive in your responses list either way, and the channel stays focused on the roles you are actively screening for.
How long do applications stay visible in Slack?
As long as your workspace retention allows — some plans trim older messages, and an archived channel goes with it. Treat Slack as the conversation and your responses list as the record, since submissions stay there until you delete them.
Related automations
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
- Drop customer feedback into your product channel
Feedback posts to #product as it arrives, with the rating and the comment, so nobody waits for a weekly roundup.
- Post event RSVPs to the planning channel
Every RSVP posts to #events with the name, party size and dietary notes, so organisers watch the headcount build in one place.
- Send each new order as a direct message
New orders arrive as a direct message to whoever packs them, with the product, quantity and address in one place.
- Send new demo requests to your sales channel
A rep sees each inbound demo request in #sales the moment it lands, and claims it with an emoji reaction before anyone else replies.
- Alert the team when a new order comes in
Each new order pings #orders with the product, quantity and buyer details, so fulfilment can start straight away.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free