Turn new acceptance criteria into tracked work
When the expected behavior changes, Notis can help make sure the added implementation work reaches GitLab.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Project Issue
Tool to create a new issue in a gitlab project. use when you need to report a bug, request a feature, or track a task within a specific project.
Why this helps
Updated acceptance criteria can quietly create extra work after the original task has already been planned.
- Keep new requirements from hiding in a spec edit.
- Give changed behavior a visible engineering follow-up.
- Reduce backtracking to discover what changed after planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and GitLab to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally to create one.
- 3Write one instruction for identifying newly added criteria that require implementation and creating an issue.
- 4Choose the Notion Page Content Updated trigger for the criteria page or data source and select a channel for run reports.
- 5Test by adding a real criterion and reviewing the issue.
Questions about this workflow
Will this trigger on a status change?
No. Page Content Updated watches body content; a property change uses Page Properties Updated.
Can it avoid creating an issue for clarifications?
Yes. Tell Notis in the prompt to create an issue only for criteria that add implementation work.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gitlab. A trigger fires from one place; an action lands in another.
Notion triggers
Gitlab actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Project
Tool to archive a project. use when you need to mark a project read-only after finishing active development. call after confirming no further changes are required.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create GitLab Group
Tool to create a new group in gitlab. use when you need to establish a new group for projects or collaboration.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Project
Tool to create a new project in gitlab. implements post /projects endpoint.
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.
Create Project Issue
Tool to create a new issue in a gitlab project. use when you need to report a bug, request a feature, or track a task within a specific project.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Repository Branch
Tool to create a new branch in a project. use when you need to create a new branch from an existing branch or a specific commit in a gitlab project.
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.
Delete Project
Tool to delete a gitlab project by its id. use when you need to remove a project, either by marking it for later deletion or deleting it immediately.
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.
Download Project Avatar
Tool to download a project’s avatar image. use when you need the raw avatar bytes after confirming the project exists.
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.
Erase Job
Tool to erase the content of a specified job within a project. use when you need to remove job artifacts and logs.
Connect any two apps with Notis in the middle.
Notion and Gitlab, 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 Gitlab.