Turn finalized project details into an SOW
Finish the project brief in Notion and let Notis prepare the statement of work from your Documenso template.
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
Use Template (v2-beta)
Tool to create a document from a template. Use when you need to instantiate a template with recipients and optional prefills.
Why this helps
Project details can be ready to go while the formal scope document waits for someone to recreate them elsewhere.
- Start the formal scope document from the finalized brief.
- Reduce duplicate entry during project kickoff.
- Give each engagement a more consistent documentation path.
Setup
Build it in a few focused steps.
- 1Connect Notion and Documenso to Notis once in the portal.
- 2Tell Notis how to recognize a finalized project brief and prepare the SOW template.
- 3Choose Page Content Updated for your project brief page as the trigger.
- 4Choose a channel for run reports and test with one finalized project brief.
Questions about this workflow
Can it tell when project details are final?
Explain your finalization signal in the prompt, such as a clear status or phrase, and test it with a representative page.
Does it send the SOW to the client?
The workflow creates a document from a template. Review the SOW before sending it for signature.
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.