Connect Notion to HackerRank Work

When something happens in Notion, 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 Notion to HackerRank Work

View example

Look up a company for SSO setup

When a company setup page is added to Notion, retrieve HackerRank Work company identifiers to help the admin start SSO configuration with the right organization.

View example

Retrieve a sign-on URL for a new request

When a Notion page records a request for a HackerRank Work SSO sign-on URL, retrieve the URL and report it with the request context.

View example

Refresh company lookup after setup notes change

When the body of a Notion SSO setup page changes, retrieve HackerRank Work company identifiers so an admin can review the directory against updated notes.

View example

Recheck companies after an SSO record changes

When properties on a Notion SSO record change, list HackerRank Work companies so the admin can recheck organization identity against the revised record.

View example

Answer an SSO URL question with a lookup

When a new comment asks for the HackerRank Work sign-on URL, retrieve it so the question can be answered from the run report.

View example

Check company identity after a setup comment

When a comment is added to the designated SSO block or page, list HackerRank Work companies so the admin can verify the organization being discussed.

View example

Retrieve the sign-on URL for a new setup subpage

When a subpage is added under the SSO project page, retrieve the HackerRank Work sign-on URL for the setup owner to review.

View example

Review company directory after setup schema changes

When the Notion SSO tracking data source schema changes, list HackerRank Work companies to support a focused review of setup records and directory context.

View example

Retrieve the sign-on URL after creating a setup view

When a new Notion view is created in the SSO setup area, retrieve the HackerRank Work sign-on URL to help the admin continue the configuration task.

Supported Triggers and Actions

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

Notion 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

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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

Comment Created

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Database Created

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

TriggerInstant

Data Source Created

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

TriggerInstant

Data Source Schema Updated

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

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.