Keep candidate follow-up context close
Update a follow-up plan in Notion and let Notis add its useful context to the candidate's Lever record.
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
Create Note
Tool to create a note on an opportunity profile or add a threaded comment to an existing note.
Why this helps
Next steps written in planning notes can disappear from view when the founder returns to the recruiting pipeline.
- Keep the next step with the candidate record.
- Reduce the effort of reopening planning notes to remember context.
- Make candidate handoffs easier to pick up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lever to Notis once through the portal.
- 2Create an automation and describe when a follow-up plan update should become a note on the matching Lever opportunity.
- 3Select Page Content Updated for the follow-up plan page or data source and choose a channel for run reports.
- 4Test with one real follow-up update and confirm the note appears in Lever.
Questions about this workflow
Can the note include a follow-up date?
Ask Notis to include a date when the Notion page contains one.
Does this send an email to the candidate?
No. This workflow adds a note to Lever and does not send candidate email.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lever. A trigger fires from one place; an action lands in another.
Notion triggers
Lever actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Opportunity Links
Tool to add links to a contact associated with an opportunity. Use when you need to attach URLs like LinkedIn profiles, GitHub accounts, personal websites, or other social media links to a candidate. Adding new links does not replace existing links.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Opportunity Sources
Tool to add sources to an opportunity. Use when you need to attribute specific recruitment channels or sources to an existing opportunity.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add Opportunity Tags
Tool to add tags to an opportunity. Use when you need to append labels or categorize an existing opportunity.
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.
Create Form Submission
Tool to create a completed profile form submission for a candidate's opportunity profile. Use when you need to submit a filled form based on an existing template.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Form Template
Tool to create a profile form template for an account. Use when you need to create a new form template with custom fields.
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.
Create Interview
Tool to create an interview on an externally-managed panel in Lever. Use when scheduling a new interview for an opportunity on a panel where externallyManaged is true.
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.
Create Note
Tool to create a note on an opportunity profile or add a threaded comment to an existing note.
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.
Create Opportunity
Tool to create a new candidate opportunity in Lever. Use when adding a new candidate to the system with automatic email-based deduplication.
Connect any two apps with Notis in the middle.
Notion and Lever, 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 Lever.