Review Leverly reattempts from a Notion lead record
Keep retry investigations close to the lead notes. Update the Notion record and have Notis retrieve the Leverly reattempt history for review.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
List Reattempts
Tool to list all reattempts in leverly. use when you need to inspect the history of ingestion reattempts before taking further action.
Why this helps
Retry investigations often get lost between the lead record and Leverly, forcing founders to reopen context and search manually.
- See retry history alongside the lead context that prompted the check.
- Reduce time spent switching between Notion and Leverly.
- Keep the next follow-up decision visible to collaborators.
Setup
Build it in a few focused steps.
- 1Connect Notion and Leverly to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis to create it conversationally.
- 3Use one plain-language prompt: when a Notion lead record is updated to request a retry review, list the matching Leverly reattempts and summarize them for review.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test by updating one real lead record to request a retry review.
Questions about this workflow
Does this stop any Leverly retries?
No. It lists reattempts for review; stopping retries requires a separate instruction and the relevant reattempt identifier.
Can the automation decide which lead to inspect?
Describe the lead context and review request in the prompt. Notis interprets the instruction and uses the connected tools.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Leverly. A trigger fires from one place; an action lands in another.
Notion triggers
Leverly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Reattempts
Tool to list all reattempts in leverly. use when you need to inspect the history of ingestion reattempts before taking further action.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Stop Leverly Reattempts
Tool to stop ongoing reattempts for a lead in leverly. use when you need to halt retries for a given reattempt id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Leverly, 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 Leverly.