Stop retry activity after a lead withdraws
A withdrawal note should not leave a retry loop running. Carry the decision to Leverly from the updated Notion record.
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
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.
Why this helps
A lead's withdrawal can be acknowledged in notes while retries continue unnoticed elsewhere.
- Act on a withdrawal where the decision is recorded.
- Prevent needless retry activity from lingering.
- Keep evidence of the stop attempt in the run report.
Setup
Build it in a few focused steps.
- 1Connect Notion and Leverly to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one prompt telling Notis to stop matching Leverly reattempts when a Notion lead record says the lead withdrew.
- 4Choose Page Properties Updated as the trigger and pick a channel for reports.
- 5Test with one real withdrawal record and an identifiable reattempt.
Questions about this workflow
Does this change the Notion record?
No. The trigger is the record update; the action is to stop matching Leverly reattempts.
What if there are multiple reattempts?
The prompt can ask Notis to inspect the available context and stop the corresponding ongoing reattempts.
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.