Skip to content
Notis

Stop LinkedIn outreach when a contact withdraws

Carry the decision to pause LinkedIn follow-up into the campaign where it matters.

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

Delete Contact From LinkedIn Campaign

Tool to delete a contact from a linkedin campaign. use when you need to remove a contact by campaign id and contact url. call after confirming the contact exists in the campaign.

Why this helps

A withdrawal recorded in a planning database can be missed while a LinkedIn sequence continues.

  • Keep LinkedIn follow-up aligned with contact decisions.
  • Reduce manual checks across planning and campaign tools.
  • Make the removal decision traceable to a Notion record.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Emelia to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis conversationally.
  • 3Describe the withdrawal status and instruct Notis to confirm the person's LinkedIn URL and target campaign before removal.
  • 4Choose Page Properties Updated for the relevant contacts data source and select a reporting channel.
  • 5Test with one withdrawn contact and verify the correct LinkedIn campaign membership is removed.

Questions about this workflow

What contact details should the record contain?

The Emelia action identifies a LinkedIn campaign contact by campaign id and contact URL. Include enough context for Notis to confirm both.

Is removal reversible?

The action removes the contact from the LinkedIn campaign. Confirm the match and decision before acting.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Emelia. A trigger fires from one place; an action lands in another.

Notion triggers

Emelia actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Contact to Blacklist

Tool to add a contact to the email blacklist. use after confirming that no further emails should be sent to a specific address. example: 'add blocked user@example.com to blacklist.'

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Contact To Campaign

Tool to add a contact to an email campaign. use when you have collected subscriber details and want to enroll them in a campaign.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Create Campaign

Tool to create a new email campaign. use after you have finalized the campaign name.

ActionInstant

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.

TriggerInstant

Create LinkedIn Campaign

Tool to create a new linkedin campaign. use when you need to launch a linkedin outreach sequence.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Create Webhook

Tool to create a new webhook for campaign events. use when you need to subscribe to activity updates after determining the campaign id and desired events.

ActionInstant

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.

TriggerInstant

Delete Contact From Campaign

Tool to remove a contact from an email campaign. use when you need to revoke a contact's subscription from a specific campaign. note: this operation is irreversible.

ActionInstant

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.

TriggerInstant

Delete Contact From LinkedIn Campaign

Tool to delete a contact from a linkedin campaign. use when you need to remove a contact by campaign id and contact url. call after confirming the contact exists in the campaign.

ActionInstant

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.

TriggerInstant

Delete Webhook

Tool to delete a specific webhook. use when you need to remove an existing webhook by url after identifying the campaign.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Emelia, 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 Emelia.