Send an interview brief to Telegram
Turn an Ashby candidate update into a concise interview brief in Telegram, with the role, stage, and relevant context available in the request.
When something happens in Ashby, Notis takes the next step in Telegram. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when an application’s e-signature request is sent, cancelled, completed or deleted.
Do this · Action
Send an answer to an inline button callback, shown as a chat notification or alert.
Turn an Ashby candidate update into a concise interview brief in Telegram, with the role, stage, and relevant context available in the request.
Convert an Ashby pipeline summary supplied to a Notis webhook into a document the hiring team can review in Telegram.
On a schedule, turn Ashby recruiting information available to the automation into a short Telegram priorities message, with any required data source specified in the prompt.
Use supplied Ashby hiring context to create a Telegram poll that helps a team quickly report recruiting blockers or focus areas.
Use supplied Ashby interview context to send an appropriate Telegram reminder for pending feedback, without claiming feedback is pending unless the request says so.
Turn job posting details supplied from Ashby into a Telegram announcement that helps the hiring team coordinate around an opening.
On a schedule, compile available candidate follow-up details into a Telegram document for review, flagging missing dates rather than treating them as stale.
Update a Telegram message with a concise candidate status summary when a webhook request supplies new recruiting context and the message to edit.
Summarize available Ashby recruiting data on a schedule and send a Telegram overview, clearly noting when historical comparison data is unavailable.
Notis builds workflows that link Ashby to Telegram. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Send an answer to an inline button callback, shown as a chat notification or alert.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Deletes a Telegram message, subject to time, message type, and chat permissions.
Triggers when an application’s e-signature request is sent, cancelled, completed or deleted.
Edits a Telegram message, subject to Telegram’s permissions and restrictions.
Triggers when a candidate submits an application or a recruiter adds one; excludes imports, syncs, and later changes.
Generate a new primary chat invite link, revoking the previous one.
Fires when an existing application changes; enabling hire or stage triggers too sends two events per action.
Forwards a Telegram message; service messages and protected content cannot be forwarded.
Fires when a candidate record is deleted, not when it is merged into another record.
Retrieve current information about a chat.
Fires when a candidate’s recent emails may have changed; messages are absent and the beta may not be enabled.
Lists chat administrators, excluding other bots.
Fires when a candidate is marked hired, including for confidential jobs.
Polls pending bot updates and filters the batch; this is not complete chat history.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Ashby and Telegram, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Telegram.