Skip to content
Notis

Move new leads from Notion into Appdrag

Capture a lead once in Notion and let Appdrag handle the next step, so promising conversations do not get buried in your notes.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Execute Cloud Backend function via POST

Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.

Why this helps

Manually re-entering lead details creates another task and makes it easy to overlook someone who is ready to hear back.

  • Starts your Appdrag lead workflow as soon as a database page is created.
  • Reduces duplicate entry during a busy day.
  • Keeps new opportunities moving without relying on memory.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Appdrag to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis conversationally to send new Notion leads to Appdrag.
  • 3Write one plain-language instruction describing how Appdrag should register each new lead.
  • 4Choose the Notion New Page trigger and a channel for run reports.
  • 5Test with one real lead entry and confirm the Appdrag function responds as expected.

Questions about this workflow

Does this copy Notion fields through a mapping screen?

No. Describe the intended outcome in the automation prompt, and Notis interprets the available Notion event and Appdrag action.

What Appdrag action does it use?

It calls an Appdrag backend function with POST, which can accept the new lead information.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Appdrag actions

Recurring trigger

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

TriggerScheduled

Execute Cloud Backend function via DELETE

Tool to execute a Cloud Backend API function via DELETE on the default environment. Use when you need to call a function with DELETE parameters and optional APIKey.

ActionInstant

Webhook trigger

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

TriggerInstant

Execute Preprod Function (DELETE)

Tool to execute the pre-production version of a Cloud Backend API function via DELETE. Use when you need to test or validate delete operations in the preprod environment before production deployment.

ActionInstant

All Page Events

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

TriggerPolling

Execute PROD API Function (GET)

Tool to execute a production Cloud Backend API function via GET. Includes robust URL handling and fallbacks to accommodate management base URLs.

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

Execute Dev Function (PATCH)

Tool to execute the development version of a Cloud Backend API function via PATCH. Use after deploying or updating your function to the dev environment.

ActionInstant

New Comment

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

TriggerPolling

Execute Cloud Backend function via POST

Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.

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

Execute Function POST (Preprod Env)

Tool to execute a Cloud Backend API function via POST on the preprod environment. Use when you need to test a function in the preprod environment before releasing to production. Include apiKey if your function requires APIKey security.

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

Execute Cloud Backend function via PUT (default)

Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.

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

Execute Cloud Backend function via PUT (preprod)

Tool to execute a Cloud Backend API function via PUT on the preprod environment. Use when you need to call a function with PUT parameters and optional APIKey in preprod.

ActionInstant

Connect any two apps with Notis in the middle.

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