Add an investor signer from a Notion record
Keep fundraising paperwork moving when the investor team changes, by adding the new signer to the confirmed Docnify document.
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
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Why this helps
Investor and advisor details can shift mid-process, leaving founders to remember which document needs another recipient.
- Reflect a new required signer on the active document.
- Reduce manual coordination when a deal team changes.
- Keep the signer update linked to the investor record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docnify to Notis once in the portal.
- 2Create an automation and describe how to confirm the document and add the intended investor recipient when the Notion record indicates one is needed.
- 3Choose Page Properties Updated for the investor data source and select a channel for run reports.
- 4Test with one real investor update and verify document identity and signing order.
Questions about this workflow
Can the signer be placed in sequence?
The action supports an optional signing order; describe the intended sequence in the prompt.
Will it add a signer to an unconfirmed document?
The instruction should require Notis to confirm the document ID and match before adding a recipient.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docnify. A trigger fires from one place; an action lands in another.
Notion triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
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.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
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 Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
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.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
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.
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Notion and Docnify, 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 Docnify.