Monitor Hiring at Target Companies Automatically
Track hiring signals at competitor and partner companies without manually checking their careers pages weekly. The moment you log them, you get their open jobs.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
Founders want to monitor hiring trends but manually checking careers pages is tedious. They skip it and miss talent or competitive intel.
- Tracks hiring signals without manual browsing
- Alerts you to growth or churn at target companies
- Feeds hiring data directly into your notes
Setup
Build it in a few focused steps.
- 1Connect Notion and Agentql to Notis.
- 2Create this automation: 'When I add a new company to my Job Tracker database, scrape their careers page and extract all open positions, required experience levels, and any salary ranges they publish.'
- 3Set trigger to 'New Page' in your Job Tracker database and choose your Notis channel.
- 4Test by adding one company and verify job listings appear in Notion.
- 5Refine to focus on specific roles (e.g., 'only engineering positions') if needed.
Questions about this workflow
How often should I refresh this data?
Set up a second automation with a weekly schedule to re-scrape companies you're actively tracking for job changes.
What if a company has no careers page?
Notis will note that, so you know to check LinkedIn Jobs or ask your network for intel.
Can I capture salary data?
Yes, if they publish it. Some companies hide ranges, so Notis will capture what's publicly available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agentql. A trigger fires from one place; an action lands in another.
Notion triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
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 Agentql, 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 Agentql.