Generate renewal letters from updated records
When a renewal record is updated, prepare a document draft that makes the next customer conversation easier to start.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Why this helps
Renewal dates and terms can sit in a database until someone remembers to build the follow-up document.
- Create a renewal draft from current recorded details.
- Make renewal follow-up easier to start on time.
- Avoid retyping dates and account information.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docugenerate to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Describe in one instruction when an updated renewal record should produce a letter and which Docugenerate template to use.
- 4Select Page Properties Updated for the renewal data source, choose a report channel, and test with one real upcoming renewal.
Questions about this workflow
Can it send the letter automatically?
This action generates the document. Review it and use your existing process to send it.
How do I prevent drafts for unrelated edits?
State the relevant renewal status or property changes in the instruction and scope the trigger to the renewal data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docugenerate. A trigger fires from one place; an action lands in another.
Notion triggers
Docugenerate actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate documents as ZIP
Tool to bulk generate multiple documents into a ZIP archive. Use when you need a batch of docs packaged as ZIP.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate document with attachments
Tool to generate a PDF with embedded attachments. Use when you need to bundle extra files into the PDF output.
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.
Generate document with merge
Tool to generate a PDF and append additional PDF files. Use when you need to merge extra pages into a generated document.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Document
Tool to update a document's metadata. Use when renaming an existing document after confirming the document 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.
Get or list templates
Tool to retrieve or list existing templates. Use when needing template IDs and metadata before making updates or generating documents.
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.
Update Template
Tool to update a template’s file and settings. Use after confirming the template ID and desired inputs.
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 Docugenerate, 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 Docugenerate.