Move new project requests into ClickUp automatically
Capture a request once in Notion and let Notis create a matching task in ClickUp, reducing the chance that an idea gets lost between workspaces.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create a task
Creates a new clickup task in a specific list, optionally as a subtask if a `parent` task id (which cannot be a subtask itself and must be in the same list) is provided.
Why this helps
New project requests can disappear in a database when the founder has to remember to recreate them in a separate task tool.
- Give each new request an actionable task
- Reduce duplicate entry between planning and execution
- Keep intake moving without relying on memory
Setup
Build it in a few focused steps.
- 1Connect Notion and ClickUp to Notis once through the portal.
- 2In Automations, create a new automation and describe creating a ClickUp task for every new project intake item in one plain-language instruction.
- 3Select the Notion New Page trigger for the relevant database and choose where Notis should report runs.
- 4Create the automation and test it with one real intake entry.
Questions about this workflow
Does this run for every new Notion page?
Choose the New Page trigger for the intended database so the automation responds to new entries there.
Do I need to map Notion properties to ClickUp fields?
No. Describe the outcome in the automation prompt and let Notis interpret the available context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clickup. A trigger fires from one place; an action lands in another.
Notion triggers
Clickup actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add dependency
Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add guest to folder
Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add guest to list
Shares a clickup list with an existing guest user, granting them specified permissions; requires the workspace to be on the clickup enterprise plan.
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.
Add guest to task
Assigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
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.
Add tag to task
Adds an existing tag to a specified task; team id is required if custom task ids is true.
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.
Add task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
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.
Add task to list
Adds an existing task to an additional clickup list; the "tasks in multiple lists" clickapp must be enabled in the workspace for this.
Connect any two apps with Notis in the middle.
Notion and Clickup, 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 Clickup.