Connect Telegram to HackerRank Work

When something happens in Telegram, Notis takes the next step in HackerRank Work. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Telegram to HackerRank Work

View example

Find a HackerRank company ID from Telegram

Ask your Telegram bot to find HackerRank company identifiers when an SSO setup task needs the right company record.

View example

Request a HackerRank SSO sign-on URL in Telegram

Let an administrator ask in Telegram for the HackerRank Work SP-initiated SSO sign-on URL and receive the result in the run report channel.

View example

Keep SSO company lookups close to the admin channel

When an administrator posts an SSO company lookup request in a Telegram channel, retrieve the HackerRank Work company list for the team.

View example

Retrieve the SSO URL when an admin taps a Telegram button

Let an administrator use an inline Telegram button to request the HackerRank Work sign-on URL and receive the result in the run report channel.

View example

Refresh a company lookup after a Telegram request is edited

When an SSO company lookup request is corrected in Telegram, retrieve the HackerRank Work company list against the updated request.

View example

Give new Telegram group admins an SSO URL lookup path

When a new member joins the Telegram admin group, retrieve the HackerRank Work sign-on URL so the team has it ready for SSO onboarding.

Supported Triggers and Actions

Notis builds workflows that link Telegram to HackerRank Work. A trigger fires from one place; an action lands in another.

Telegram triggers

HackerRank Work actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

List Companies

Tool to list all companies and their unique identifiers. Use when you need the company_unique_id for SSO metadata retrieval.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Consume SAML Assertion

Tool to consume SAML assertions. Use when receiving SAMLResponse and RelayState from the Identity Provider for SSO sign-in.

ActionInstant

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.

TriggerInstant

Get SSO Sign-On URL

Tool to get the SP-initiated SSO sign-on URL. Use when configuring SAML SSO with your identity provider.

ActionInstant

New Channel Post

Triggered when a new post is published to a channel where your bot is an administrator.

TriggerInstant

Callback Query Received

Triggered when a user taps an inline keyboard button attached to one of your bot's messages.

TriggerInstant

Message Edited

Triggered when a message in a chat your bot can see is edited by its sender.

TriggerInstant

New Chat Member

Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.

TriggerInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

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.