Recover signing requests after contact corrections
When the contact details are corrected in Notion, let Notis resend the matching document for signing to help get the process back on track.
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
Resend Document For Signing V1
Tool to re-send a document for signing via POST /api/v1/documents/{id}/resend.
Why this helps
A signing request sent to incorrect contact details can become a quiet blocker unless someone remembers to resend it.
- Make a contact correction a clear follow-up cue.
- Reduce the chance that a corrected request remains unsent.
- Keep the resend tied to the agreement record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Documenso to Notis once in the portal.
- 2Describe when a corrected contact should cause the corresponding signing request to be resent.
- 3Choose Page Properties Updated for your agreement tracker as the trigger.
- 4Choose a run-report channel and test with a known pending document and corrected contact.
Questions about this workflow
Will it resend every time any property changes?
State the contact correction condition clearly in the prompt and test the behavior before relying on it.
What document should be resent?
Describe how the Notion record identifies the pending Documenso document. The resend action requires a valid document with pending recipients.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Documenso. A trigger fires from one place; an action lands in another.
Notion triggers
Documenso actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Embedding Presign Token V2 Beta
Tool to create a presign token for embedded authoring sessions. Use when initializing or renewing an embed session token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Document Fields
Tool to delete one or more fields from a document. Use when you have confirmed the field IDs to remove. Supports single-field and batch deletion.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Template
Tool to delete a template by ID.
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.
Distribute Document V2
Tool to distribute a document for signing. Use when you need to send a document to all or specific pending recipients.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Download Signed Document
Tool to download a signed document file. Use when you need to retrieve the finalized PDF after a document has been signed.
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.
Duplicate Document V2
Tool to duplicate a document. Use when you need to create an exact copy of an existing document. Ensure the source document ID is valid before calling.
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.
Find Documents V2
Tool to find documents. Use when retrieving a paginated list of documents for operations requiring a document ID.
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.
Get Template
Tool to fetch a template by ID.
Connect any two apps with Notis in the middle.
Notion and Documenso, 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 Documenso.