Carry recipient decisions from Notion into report settings
When a reporting discussion settles a recipient change, prompt the existing report update while the decision is easy to act on.
Trigger
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.
Action
Update Report
Tool to update an existing report’s configuration. use when you need to modify the schedule, recipients, or format of a scheduled report.
Why this helps
Recipient decisions can be documented in a thread and then forgotten when report settings live elsewhere.
- Reduce follow-up after recipient decisions are recorded.
- Keep scheduled report recipients in step with the discussion.
- Avoid hunting down the report setting later.
Setup
Build it in a few focused steps.
- 1Connect Notion and DigiCert to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to set it up in plain language.
- 3Tell Notis to update the named existing DigiCert report when a recipient decision is added as a comment on the designated page, select Comment Created, choose a report channel, and test with one real comment. Enable Read comments and reauthorize if needed.
Questions about this workflow
Should any comment update the report?
Use a designated reporting page and clearly tell Notis what decision qualifies and which existing report to update.
Can this change the report schedule too?
The action supports updating schedule, recipients, or format. Specify the requested change in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Digicert. A trigger fires from one place; an action lands in another.
Notion triggers
Digicert actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Permission
Tool to check if a specific permission is available. use when validating that the authenticated user may perform an operation before attempting it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create API Key
Tool to create a new api key with specified permissions. use when you have a valid digicert user id and need to generate a new key. note the api key appears only once; save it securely.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List API Access Roles
Tool to retrieve a list of available api access roles. use after confirming authentication with an api key.
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.
List Intermediate Certificates
Tool to retrieve a list of intermediate certificates. use when you need to list all intermediate certificates for your account. no input required.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List CertCentral Users
Tool to retrieve a list of certcentral account users. use when you need to audit or manage users with support for pagination and optional detail inclusion.
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.
Update Report
Tool to update an existing report’s configuration. use when you need to modify the schedule, recipients, or format of a scheduled report.
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.
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 Digicert, 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 Digicert.