Keep corrected candidate details visible in Ashby
A correction to a candidate update should reach the place where the hiring team works.
Trigger
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Action
Create Candidate Note
Create a note on a candidate profile. Use this to add comments, observations, or feedback about a candidate during the recruitment process.
Why this helps
Edits in chat can be easy to miss, leaving recruiting decisions based on outdated context.
- Notice candidate-related corrections as they arrive.
- Keep the latest context available on the Ashby profile.
- Reduce confusion from stale details in earlier messages.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Ashby to Notis once through the portal.
- 2Create an automation in the portal or describe it to Notis conversationally.
- 3Write one instruction that limits notes to meaningful candidate-related corrections and identifies the right profile.
- 4Choose Telegram Message Edited as the trigger and select where Notis reports runs.
- 5Test by editing one real candidate update and checking the resulting Ashby note.
Questions about this workflow
Will the workflow replace an earlier Ashby note?
The selected action creates a note. Instruct Notis to make clear that the note records a correction and reference what was updated.
Can it process an edit without candidate context?
It should act only when the edit can be matched to a candidate and contains a meaningful recruiting correction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Ashby. A trigger fires from one place; an action lands in another.
Telegram triggers
Ashby actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Candidate to Project
Add a candidate to a project in Ashby. Projects are sourcing initiatives or recruiting campaigns used to organize and track candidate pipelines. Use this to associate candidates with specific sourcing efforts. Common use cases: - Adding sourced candidates to recruiting campaigns - Organizing candidates by sourcing channel or initiative - Tracking candidates in specific hiring projects Requires candidatesWrite permission. Returns the updated candidate object on success, or error details if the candidate or project is not found.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Candidate Tag
Add a tag to a candidate in Ashby. Use this to categorize and organize candidates with existing tags from the system. This action allows you to apply labels/tags to candidates for filtering, searching, and organizational purposes. Tags must already exist in the system - use LIST_CANDIDATE_TAGS to view available tags or CREATE_CANDIDATE_TAG to create new ones. The response includes the full updated candidate object when successful, showing the newly added tag in the candidate's tags array. If a candidate already has the tag, the operation will still succeed idempotently.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Add Hiring Team Member
Add an Ashby user to a hiring team at the application, job, or opening level. Use this when you need to assign a team member to participate in the hiring process with a specific role. Requires the organizationWrite permission.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Add User to Interviewer Pool
Add a user to an interviewer pool. Use this to assign interviewers to interview pools for scheduling and coordination. Requires the hiringProcessMetadataWrite permission.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Add Opening Job
Adds a job to an opening (job requisition) in Ashby ATS. An opening represents a position to be filled, while a job defines the role details. This action associates an existing job with an existing opening, allowing multiple jobs to be linked to a single opening. Use this when you need to add job definitions to an opening or when creating multi-role requisitions. Requires the jobsWrite permission. On success, returns the updated opening with the job added to its jobIds array. On failure, returns error details with specific error codes.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Add Opening Location
Tool to add a location to an opening (job requisition). Use when you need to associate a location with an existing opening. Requires the jobsWrite permission.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Anonymize Candidate
Anonymize a candidate by removing personally identifiable information. Use this when you need to permanently anonymize a candidate's data. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
Approve Offer
Approve an offer or a specific approval step within an offer's approval process. This action supports two modes: - Complete offer approval: Provide only offerId to approve the entire offer - Step-specific approval: Provide offerId, approvalStepId, and userId to approve a specific step When approving a specific step, both approvalStepId and userId are required together. Requires the 'offersWrite' permission.
Connect any two apps with Notis in the middle.
Telegram and Ashby, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ashby.