Prepare LaunchDarkly rollout triggers from accepted requests
An accepted request can move into rollout planning with its LaunchDarkly trigger workflow ready to coordinate.
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
Create Flag Trigger Workflow
Tool to create a flag trigger workflow. use when setting up an automated trigger to toggle a flag in a specific environment.
Why this helps
Accepted requests can fall between product tracking and engineering rollout preparation.
- Makes accepted requests easier to carry into rollout planning.
- Reduces manual translation between product notes and flag setup.
- Leaves a trigger workflow connected to the request context.
Setup
Build it in a few focused steps.
- 1Connect Notion and LaunchDarkly to Notis once through the portal.
- 2Create an automation and describe which accepted request pages should lead to a flag trigger workflow.
- 3Pick the Notion Page Created trigger for the relevant request parent or data source.
- 4Choose a channel for run reports, then test with one real accepted request.
Questions about this workflow
Can this distinguish accepted requests from all requests?
Use a trigger scoped to the appropriate Notion source when available and describe the acceptance context in the instruction.
What does the LaunchDarkly action create?
It creates a flag trigger workflow. It does not create a feature flag or independently approve the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Launch darkly. A trigger fires from one place; an action lands in another.
Notion triggers
Launch darkly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Flag Trigger Workflow
Tool to create a flag trigger workflow. use when setting up an automated trigger to toggle a flag in a specific environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Trigger Workflow
Tool to delete a specific flag trigger workflow. use after confirming the project key, feature flag key, environment key, and trigger workflow id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Custom Roles
Tool to retrieve a list of all custom roles. use when you need to list roles for permissions audits or configuration reviews. note: results are paginated.
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 Environments
Tool to retrieve a list of all environments within a project. use after confirming the project key; supports pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Code Reference Repositories
Tool to list code reference repositories. use when retrieving repositories for a specific project; includes pagination.
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.
List Projects
Tool to retrieve a list of all projects. use after confirming credentials to enumerate project keys and metadata.
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.
List Teams
Tool to list all teams in launchdarkly. use after confirming credentials; supports pagination internally.
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.
Connect any two apps with Notis in the middle.
Notion and Launch darkly, 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 Launch darkly.