Refresh the company lookup when SSO notes change
When setup details change, get a fresh view of HackerRank Work companies in the run report. Notis uses a Notion content update as the cue to repeat the lookup.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
List Companies
Tool to list all companies and their unique identifiers. Use when you need the company_unique_id for SSO metadata retrieval.
Why this helps
People may keep working from an old directory lookup after the setup notes or organizational context has changed.
- Prompt a fresh company lookup after relevant page edits.
- Make changed setup context easier to notice during review.
- Avoid relying on an old result when resuming work.
Setup
Build it in a few focused steps.
- 1Connect Notion and HackerRank Work to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis to retrieve HackerRank Work company identifiers when the designated SSO setup page content changes.
- 3Select the Notion Page Content Updated trigger and scope it to the setup page or its data source.
- 4Choose a run-report channel, then test by making a meaningful update to the real setup notes.
Questions about this workflow
Will every keystroke start a run?
Notion aggregates page content edits within a short window, so a burst of edits is generally reported together.
Does the lookup confirm which company is correct?
No. The action lists company identifiers; an admin still needs to confirm the appropriate organization.
When this happens · Trigger
Do this · Action
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.
List Companies
Tool to list all companies and their unique identifiers. Use when you need the company_unique_id for SSO metadata retrieval.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Consume SAML Assertion
Tool to consume SAML assertions. Use when receiving SAMLResponse and RelayState from the Identity Provider for SSO sign-in.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get SSO Sign-On URL
Tool to get the SP-initiated SSO sign-on URL. Use when configuring SAML SSO with your identity provider.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and HackerRank Work, 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 HackerRank Work.