Open the relevant Doppler log entry from an incident update
Connect an incident update to the specific config log entry that helps explain the change.
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
Retrieve Config Log Entry
Tool to retrieve a specific config log entry. Use when needing details of a single config log; call after specifying project, config, and log identifiers.
Why this helps
An incident record can mention a configuration change while the detailed audit entry remains a separate manual lookup.
- Surface detailed audit context from an incident update.
- Spend less time searching for a specific change record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Doppler secretops to Notis once.
- 2Create an automation in the portal or ask Notis for one in plain language.
- 3Write one instruction asking Notis to retrieve the specific Doppler config log entry identified in the incident update.
- 4Pick the Notion Page Content Updated trigger for the incident page and choose a report channel.
- 5Test with an update that references a valid config log and check the returned entry.
Questions about this workflow
What does this action need to retrieve a log entry?
It needs a valid config identity and log identifier. The prompt should explain where to find those in the incident context.
Can this action undo the change?
No. It retrieves a log entry; rollback is a separate action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Doppler secretops. A trigger fires from one place; an action lands in another.
Notion triggers
Doppler secretops actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Activity Logs List
Tool to list workplace activity logs. Use when you need to fetch recent activity logs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve Activity Log
Tool to retrieve a single activity log entry by id. Use when you have a valid Activity Log id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve Config Log Entry
Tool to retrieve a specific config log entry. Use when needing details of a single config log; call after specifying project, config, and log identifiers.
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.
Config Logs List
Tool to list config change logs for a specific config. Use when you need the audit trail for a config after confirming its identity.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Config Logs Rollback
Tool to rollback a config to a selected log version. Use when needing to undo a specific change by its log ID, after confirming project, config, and log ID.
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.
Clone Config
Tool to clone a branch config including all its secrets. Use after confirming the source config details.
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.
Create Branch Config
Tool to create a branch config. Use when you need to programmatically establish a new branch-based configuration for a specified project and environment. Use after selecting the target project and environment.
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.
Configs Delete
Tool to delete a config permanently. Use when you need to remove a config that is no longer needed.
Connect any two apps with Notis in the middle.
Notion and Doppler secretops, 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 Doppler secretops.