Keep DocsAutomator settings aligned with a Notion brief
When the brief changes, the document workflow may need a specific settings update. Tell Notis which automation and fields are approved to 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
Update Automation
Tool to update an existing automation's settings in DocsAutomator. Only the fields included in the request are updated. Use when you need to modify automation properties like title, template link, locale settings, or activation status.
Why this helps
A revised brief can leave a separate document workflow using outdated settings unless someone remembers to revisit it.
- Attach a clear configuration follow-up to a brief revision.
- Reduce the number of places to remember when a process changes.
- Make the intended automation update explicit and reviewable.
Setup
Build it in a few focused steps.
- 1Connect Notion and DocsAutomator to Notis once in the portal.
- 2Create an automation in the portal or ask Notis for the outcome in plain language.
- 3Specify which Notion brief changes warrant an update and name the DocsAutomator automation and settings to change.
- 4Select Page Content Updated, scoped to the relevant page, and choose a report channel.
- 5Test with one real brief edit and inspect the DocsAutomator settings that changed.
Questions about this workflow
Will any text edit update the automation?
The trigger detects page content edits. State in the instruction which kinds of edits justify a change and the precise setting to update.
Does this edit a DocsAutomator template?
The selected action updates automation settings, such as title, template link, locale, or activation status. It does not directly edit template text.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docsautomator. A trigger fires from one place; an action lands in another.
Notion triggers
Docsautomator actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Automation
Tool to create a new DocsAutomator automation with specified data source and optional Google Doc template. Use when you need to set up a new document automation workflow. PDF templates must be uploaded through the DocsAutomator app interface.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Automation
Tool to permanently delete an automation and all associated data. Use when you need to remove an automation that is no longer needed. This action cannot be undone.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Duplicate Automation
Tool to create a copy of an existing automation with ' COPY' appended to the title. Use when you need to duplicate an existing automation without recreating it from scratch.
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 Automation Details
Tool to retrieve details of a specific automation by its ID. Use when you need to fetch configuration, data source settings, and template information for an automation.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Queue Statistics
Tool to retrieve current document generation queue statistics for your workspace. Use when monitoring queue health or checking processing capacity.
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 Automations
Tool to retrieve all automations in your workspace with their basic details. Use when you need to view, list, or enumerate existing automations.
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 Signing Sessions
Tool to retrieve signing sessions with optional filtering by status or signer email. Returns paginated results. Use when you need to list or search for signing sessions in DocsAutomator.
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.
Send Test Email
Tool to send a test email with a sample PDF attachment to verify email configuration. Use when you need to test email delivery for a specific automation. Rate limited to 25 emails per hour per automation.
Connect any two apps with Notis in the middle.
Notion and Docsautomator, 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 Docsautomator.