Keep Ignisign document details current
Make a content change to the agreement in Notion and let Notis refresh the matching Ignisign document information.
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 Document Information
Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation.
Why this helps
Document labels and descriptions can drift from the agreement people are reviewing, making the right file harder to identify.
- Keeps document descriptions aligned with the working agreement.
- Makes files easier to recognize in Ignisign.
- Reduces small administrative corrections before signing.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ignisign to Notis once through the portal.
- 2Create an automation that updates the corresponding Ignisign document information when agreement page content changes.
- 3Choose the Notion Page Content Updated trigger and the channel for run reports.
- 4Test with one agreement edit and review its Ignisign document details.
Questions about this workflow
Does this change the document's actual file content?
No. This action updates document metadata such as its label, description, or external identifier.
What should trigger a metadata refresh?
Use the instruction to specify the agreement edits that affect how the document should be identified.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ignisign. A trigger fires from one place; an action lands in another.
Notion triggers
Ignisign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ignisign API Authentication
Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cancel Signature Request
Tool to cancel a signature request. Use after identifying the signature request to abort.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Initialize Document
Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
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.
Create Signer
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Webhook Endpoint
Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
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.
Delete Document
Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
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.
Delete Ignisign Signature Request
Tool to delete a signature request. Use when you need to permanently remove a signature request by its 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.
Delete Signer
Tool to delete a signer. Use when you need to remove a signer from a specific application environment after confirming signer ID.
Connect any two apps with Notis in the middle.
Notion and Ignisign, 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 Ignisign.