Review candidate follow-ups without losing the thread
Bring candidate follow-ups together in one review document, with uncertainty made clear.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Document
Send general files (documents) to a telegram chat using the bot api.
Why this helps
A candidate can be overlooked when follow-up dates and next steps are scattered across busy recruiting work.
- Review multiple follow-ups in one document.
- Use dates and criteria supplied to the automation.
- Flag records that lack enough information for a reliable follow-up decision.
Setup
Build it in a few focused steps.
- 1Connect Ashby and Telegram once in the Notis portal.
- 2Create an automation in Automations, New Automation, or describe it to Notis in plain language.
- 3Ask Notis to prepare a follow-up review from available candidate details and clearly flag missing dates or next steps.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real recruiting example and confirm the needed candidate details are available.
Questions about this workflow
How does it decide a candidate is stale?
Define the review window in your instruction and make sure the automation has dated status information. Without those details, it should flag uncertainty rather than label a candidate stale.
Does the schedule read candidate records from Ashby?
Not by itself. The package does not specify an Ashby trigger or data-fetch action, so the scheduled automation needs access to relevant recruiting information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ashby to Telegram. A trigger fires from one place; an action lands in another.
Ashby triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Ashby and Telegram, 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 Telegram.