Route job applications to a private hiring chat
Applications land in a private hiring chat with the role, name and start date, so reviewers can weigh them together.
New submission on your "Job application" form
Send a message to a private hiring chat in Telegram
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring in a small team means three or four people reading the same applications between other jobs. Putting each one into a private chat gives everyone the role, the name and the start date at the moment it lands, instead of a weekly forward from whoever owns the inbox.
Reviewers can talk about a candidate by replying to the bot's message, which keeps the discussion next to the application. Those replies live in Telegram only — nothing typed in the chat is written back into the form or the response.
Setting it up
- 1
Publish the application form and submit a dummy application so Zapier can map every answer from a complete example.
- 2
Create a private group containing only the reviewers, add the bot, and decide before anyone joins whether new members should see earlier candidates.
- 3
Set formformform's "New Submission" trigger to the application form. If one form covers several roles, keep it on a single Zap and let the role do the sorting inside the message.
- 4
Open the Telegram message with Position Applied For, so a reviewer can scan the chat for the vacancy they own.
- 5
Add Full Name and Available Start Date underneath — between them they settle most first-pass decisions.
- 6
Map Relevant Skills next, and deliberately leave Work Experience and Cover Letter out. Both run long, and a wall of text is worse than a link in a chat people read on a phone.
- 7
End the message with a fixed line pointing at your formformform responses, so anyone can open the full application from the chat.
- 8
Send the test, agree with reviewers that notes go in replies to the bot's message, then turn 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 | Telegram |
|---|---|
| Position Applied For | First line of the message, as the sort key |
| Full Name | Second line, naming the candidate |
| Available Start Date | Beside the name, for scheduling |
| Relevant Skills | Third line, the short screening summary |
| Email Address | Closing line, for whoever books the call |
Variations worth knowing
Filter on Position Applied For and give each open role its own Telegram chat with only the reviewers for that role in it. Hiring managers stop scrolling past applications for jobs they are not involved in, and all the Zaps still watch one form.
Ask reviewers to reply directly to the bot's message rather than starting a new one. Telegram keeps the quoted candidate visible above each note, so a scroll back through the chat reads as one thread per applicant.
If something isn't arriving
Position Applied For was optional, or the sample submission Zapier learned from skipped it. Make the question required in the form, submit a new test, and remap the field so every message opens with a role a reviewer recognises.
Telegram can hide a private group's history from new members. Open the group settings and make chat history visible to new members, or re-post the applications still in play. The submissions themselves are all in formformform regardless.
Frequently asked questions
Can candidates see anything in the hiring chat?
No. The bot posts into a private group you control, and applicants have no access to it. They see only the form and its confirmation. Keep the group private and be deliberate about who you add to it.
Does a decision made in the chat update the application?
No. The flow runs one way, from the form into Telegram, and nothing is written back into the response. Track status in whatever tracker or spreadsheet you already use, and treat the chat as the discussion.
How do I stop applications for a closed role from posting?
Add a Zapier filter on Position Applied For so the closed role is skipped, or remove that option from the form in formformform. Removing the option is cleaner, since it also stops people applying for something that no longer exists.
Related automations
- Broadcast every new order to a channel
New orders post to your orders channel with the product, quantity and buyer details, so packing can start straight away.
- Get feedback in a direct chat with your bot
Feedback goes straight to a one-to-one chat with your bot, so you see the rating and the comment as they arrive.
- Keep organisers updated on event RSVPs
Each RSVP posts to the organisers group with the attendee name and the session they picked, as people sign up.
- Post support requests to your team chat
Each support request arrives in your team chat with the priority first, so whoever is on shift can pick it up from a phone.
- Send new quote requests to your sales group
Every quote request lands in your sales group in Telegram with the name, company, budget and timeline a rep needs to reply.
- Alert a recruiter to every new application
The recruiter gets a nudge for every applicant, with enough to decide who to call first.
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