Give a new Notion task page Leiga issue context
If a new task page points to existing delivery work, bring the Leiga issue details into the moment the task is created.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
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.
Why this helps
A task can be documented without the issue context needed to understand ownership, scope, or progress.
- Attach useful delivery context to a new task discussion.
- Reduce time spent locating an already-known issue.
- Help collaborators start with a fuller picture.
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 conversationally.
- 3In one instruction, ask Notis to find a Leiga issue number in the new task page and retrieve that issue's details.
- 4Select the Notion Page Created trigger for the task data source and choose a report channel.
- 5Test with a real task page that contains a valid issue number.
Questions about this workflow
What if the page does not include an issue number?
Tell Notis in the instruction to skip the lookup unless the page includes a usable Leiga issue number.
Does this create or update an issue?
No. The workflow retrieves issue details for context.
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.