Post new job applications to your hiring channel
Every application posts to #hiring with the role and candidate name, so the panel can react in the thread instead of forwarding it round.
New submission on your job application form
Send a channel message to the #hiring channel with the role and candidate details
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring stalls in the gap between an application arriving and the panel seeing it. Posting each submission into #hiring puts the role and the candidate in front of everyone at once, and a thumbs-up or a one-line reply is enough to say worth a screen without anyone opening a tracker.
Teams that hire in bursts get the most from it: a few roles open, a panel of three or four. The application text stays in formformform, and the channel carries just enough to make the first call.
Setting it up
- 1
Publish your application form from the Job Application Form template, and make Position Applied For a dropdown of open roles rather than free text so the channel reads consistently.
- 2
In Zapier, watch that one form with the New Submission trigger. If you run a separate form per role, build a Zap per form rather than sorting them out downstream.
- 3
Add the Microsoft Teams Send Channel Message action and select #hiring in the team your panel already works in.
- 4
Set the message title to Position Applied For followed by Full Name, so the channel list reads as a list of candidates grouped by role.
- 5
Map Available Start Date and Employment Type onto one line underneath, since those two answers rule people in or out fastest.
- 6
Put Relevant Skills in the body as its own block, and leave Cover Letter out of the message — read that in the submission rather than filling the channel with it.
- 7
Add Email Address at the foot so whoever claims the candidate can reply to them directly.
- 8
Run one test application through the live form, check the title on mobile Teams where it truncates soonest, 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 | Microsoft Teams |
|---|---|
| Position Applied For | Start of the message title |
| Full Name | Message title, after the role |
| Available Start Date | Summary line under the title |
| Employment Type | Summary line, next to the start date |
| Relevant Skills | First block of the message body |
| Email Address | Contact line at the foot of the message |
Variations worth knowing
With several roles running at once, add Zapier paths on Position Applied For and post each role into its own channel, so a panel only ever sees the candidates it is actually interviewing this month.
Add a filter on Employment Type or Available Start Date so speculative and long-notice applications skip the channel and stay in the responses list, keeping #hiring to candidates the panel can move on now.
If something isn't arriving
Two Zaps are watching the same form, usually a copy left running after testing. Filter the Zap list by the formformform trigger and turn the duplicate off rather than deleting it, so its task history survives.
Position Applied For is passed through exactly as the candidate typed it. Change the question from free text to a dropdown of your open roles in the form editor and the channel titles line up again.
Frequently asked questions
Can the panel score candidates from the Teams message?
Reactions work as a light signal, and many panels use a thumbs-up to mean screen this one. Those reactions live in Teams alone and are never written back onto the submission, so record the real decision wherever you track hiring.
Who can see the applications once they are posted?
Everyone in the team that owns #hiring. Applications carry personal details, so put the channel in a private team limited to the panel if your wider workspace is open, and keep the full submission in formformform.
Can we reply to the candidate from Teams?
No. The message is a notification to your own team and carries no reply path back to the applicant. Write to the address mapped into the message, or add an email action to the same Zap for an acknowledgement.
Related automations
- Post event registrations to the events channel
Every registration posts to #events with the attendee and ticket type, so organisers see numbers build during a campaign in real time.
- Post feedback scores to the product channel
Each response posts to #product-feedback with the score and the comment behind it, so verbatims get read rather than exported quarterly.
- Post new sales enquiries into your leads channel
Each contact sales submission lands in #leads with company, size and timeline included, so a rep can reply the same hour.
- Post support requests into a triage channel
Every support request posts to #support-triage with its subject, priority and requester, so agents watch one channel instead of an inbox.
- Send rush orders straight to the lead on shift
Orders marked rush go out as a private chat to the fulfilment lead, with the job details, rather than waiting in a busy channel.
- 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.
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