Keep opt-out decisions connected to your outreach record
Record a contact's preference in Notion and make it easier to carry that decision into Instantly.
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
Update Lead Interest Status
Tool to update a lead's interest status. Use when you need to set or reset a lead’s interest status for follow-up actions.
Why this helps
Important contact preferences can be missed when they are recorded separately from the outreach tool.
- Keep contact decisions visible across your workflow.
- Reduce repeated checking between records.
- Make preference follow-through easier to complete.
Setup
Build it in a few focused steps.
- 1Connect Notion and Instantly to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3In one instruction, ask Notis to update the corresponding Instantly lead's interest status when a Notion contact is explicitly marked opted out.
- 4Select Page Properties Updated scoped to the contact data source and choose a channel for run reports.
- 5Test with one real opt-out record and review the corresponding lead status in Instantly.
Questions about this workflow
What event should activate this?
Use an explicit opt-out status in the contact record and specify the resulting Instantly interest status.
Does this delete the lead?
No. This action updates interest status; it does not delete the lead.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Instantly. A trigger fires from one place; an action lands in another.
Notion triggers
Instantly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Email Verification Status
Tool to check status of an email verification job. Use after submitting a verification request to retrieve the current status of a specific email address.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count Unread Emails
Tool to retrieve the count of unread emails. Use when you need to know how many unread messages are in your inbox before sending new emails.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create AI Enrichment
Tool to create an AI enrichment job for a campaign or lead list. Use when you need to enrich a resource with AI-driven insights.
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 API Key
Tool to create a new API key. Use when you need to generate credentials for programmatic access to the Instantly API.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Campaign
Tool to create a new campaign. Use when you have campaign details ready and want to launch.
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 Inbox Placement Test
Tool to create an inbox placement test. Use when you need to measure deliverability across providers with your prepared email and recipient list.
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 Lead
Tool to create a new lead. Use when you need to add an individual lead to a campaign.
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 Lead List
Tool to create a new lead list. Use when you need to organize leads into a dedicated list before importing them into campaigns.
Connect any two apps with Notis in the middle.
Notion and Instantly, 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 Instantly.