Make H-1B salary research easier to resume
A monthly check can surface the next company to research without rebuilding your workflow each time.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get H-1B salaries
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
Why this helps
Detailed visa salary research is easy to postpone when there is no clear recurring moment to pick it back up.
- Create a recurring cue to revisit company research.
- Make it easier to resume an ongoing research queue.
- Reduce the effort of deciding where to restart.
Setup
Build it in a few focused steps.
- 1Connect Notion and Levels.fyi to Notis once in the portal.
- 2Create an automation or ask Notis to run a monthly H-1B research review.
- 3Describe in one plain-language prompt which tracked companies to review and what salary data to retrieve.
- 4Choose a monthly schedule and a channel for run reports.
- 5Test with one real company in your research queue and review the result.
Questions about this workflow
Can the check use my existing company queue?
Describe where the queue lives in Notion and how Notis should identify entries for review.
Will every company have a record?
The workflow retrieves available Levels.fyi H-1B salary data; records may not be available for every company.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Levels.fyi. A trigger fires from one place; an action lands in another.
Notion triggers
Levels.fyi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get company benefits
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get salary summary
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get salary data
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
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.
Get H-1B salaries
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get internship salaries
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
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.
Get company overview
Access real compensation data, benefits packages, and salary trends across tech companies and job levels. Retrieve internship pay, H-1B visa salary records, company profiles, and detailed breakdowns by role and level.
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 Levels.fyi, 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 Levels.fyi.