Create a Leiga project from each Notion brief
Capture the brief once in Notion and let Notis create its matching Leiga project, so a promising idea has a clear home for delivery.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Project
Tool to create a new project in Leiga. Use after gathering project details and authenticating.
Why this helps
A project brief can sit in Notion while someone still has to recreate it in the team’s delivery tool.
- Avoid re-entering project details in two tools.
- Give new work a Leiga home as soon as its brief is ready.
- Keep project setup moving without another context switch.
Setup
Build it in a few focused steps.
- 1Connect Notion and Leiga to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set one up conversationally.
- 3In one instruction, tell Notis to use each new project brief to create a Leiga project with the relevant details.
- 4Select the Notion New Page trigger for the project brief database and choose a channel for run reports.
- 5Test with one real project brief and review the created Leiga project.
Questions about this workflow
Does this create a Leiga project for every new Notion page?
Set the instruction and trigger around the project brief database so the automation applies to the intended new items.
Do I need to map Notion properties to Leiga fields?
No. Describe the desired outcome in one plain-language instruction for Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Leiga. A trigger fires from one place; an action lands in another.
Notion triggers
Leiga actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Project
Tool to create a new project in Leiga. Use after gathering project details and authenticating.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get File List
Tool to retrieve a paginated list of files in a specified directory. Use after obtaining the directory ID to view files.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Issue Detail by Number
Tool to fetch detailed information about a specific issue using its issue number. Use when you have an issue number and need complete issue details.
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.
Get Issue Schema
Tool to retrieve the issue custom-field schema. Use when you need the full list of field configurations after selecting an issue type.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Project Information
Tool to fetch detailed information about a specific project by its ID. Use when you need complete project metadata, including owner and members.
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.
Get Project Overview Template
Tool to retrieve the project overview template. Use when you need the structured overview template for a project after confirming its 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.
Get Project Template List
Tool to retrieve a list of project templates. Use when browsing available templates before creating a new project.
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.
Get Version List
Tool to fetch list of versions for a specific platform. Use when you need to view all available versions before deployment.
Connect any two apps with Notis in the middle.
Notion and Leiga, 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 Leiga.