We developed a MAX bot for candidates and staff in a workforce outsourcing business. The new channel connects to the same 1C system as the existing Telegram bots: applications enter the HR system, while shift offers and staff replies pass through MAX.
All case studies
MAX bot for candidates and staff
Candidate applications, shift offers and staff replies in MAX, connected to 1C through n8n. The existing Telegram channel remains in operation.
Images3Video1
SolutionMAX bot with 1C and n8n
StatusAcceptance testing and final fixes
Project interface
Screens from the project.
Select a screen to open the full image.
Project video
See the solution in action.
Play the recording, seek to any point or open it full screen.
Client task and starting point
Candidates already applied through Telegram, while staff received shift offers and replied in the messenger. Candidates, employees and shifts were managed in 1C.
The client needed an equivalent MAX channel while retaining the working Telegram integration and familiar 1C documents and manager actions. MAX had to transfer applications, link users to staff records and return shift replies.
What was implemented
Two MAX bot workflows — candidate and employee — with a separate n8n workflow, 1C exchange and parallel operation of the existing Telegram channel.
- Candidate menu: Submit application, Vacancies and About the company.
- An application with full name, phone and email, personal-data consent and automatic transfer to the 1C candidate directory.
- An internal MAX identifier links the messenger user to the 1C record.
- After a manager action in 1C, the candidate becomes an employee; the bot notifies the user of the new status.
- Shift offers are sent to staff in the required branch, with location, department, date, time and conditions.
- Accept and Decline replies return to 1C, where shift responses are loaded and displayed.
- Integration with the «Заявка на рабочую смену» (shift request) and «Рабочая смена» (work shift) documents, a separate MAX broadcast button and retrieval of staff who volunteer for a shift.
- The 1C extension was updated to resolve conflicts between MAX and Telegram commands.
- A separate n8n workflow for MAX and hosting on a Timeweb cloud server.
How the solution works
- 01
Candidate application
The candidate starts the MAX bot, completes the application and gives personal-data consent. n8n transfers the application to 1C and creates a candidate record.
- 02
Employee status
After speaking with the candidate, the manager creates an employee record from it in 1C. The record is linked to the MAX user through an internal identifier, and the bot sends a status notification.
- 03
Shift offer
The manager launches a MAX broadcast from the shift-request document. Staff in the required branch receive a card with the shift parameters and conditions.
- 04
Reply in 1C
The employee accepts or declines. The reply returns to 1C, where the manager receives responses and continues working with the shift.
Technical logic and integrations
MAX Bot API connects to 1C through a separate n8n workflow and HTTP/webhook exchange. The bot runs on a Timeweb cloud server.
An internal MAX identifier links the messenger user to the candidate and then the employee record in 1C; identifier values are not published.
MAX is integrated into existing 1C HR documents and workflows. Telegram runs in parallel, with command conflicts in the 1C extension resolved.
MAX Bot API1Cn8nTelegramHTTP / WebhooksTimeweb
Business value
The client gained an additional MAX channel for candidates and staff while retaining the existing Telegram workflow.
Applications reach 1C automatically without repeated manual entry. Once an employee record is created, staff can receive shift offers and their replies return to the same HR system.
Managers continue to handle candidates, employees and shifts in the familiar 1C interface.
In September 2026, development reached final testing and acceptance. The supplied materials report an end-to-end test of candidate → employee → shift offer → reply → processing in 1C. Final client comments were being addressed during acceptance testing.
Have a similar workflow?Tell us what needs to change. We can discuss the working logic without a long questionnaire.
Discuss a similar project Have a similar task?