Bring signature status into your review routine
Make pending agreements easier to scan when you sit down to review.
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
List Documents
Tool to list documents for a business. use when you need to retrieve documents with optional filters after setting business id in query params.
Why this helps
Checking scattered signature requests requires switching tools and remembering which agreements need attention.
- Make an Eversign document check part of an established Notion review.
- Reduce time spent locating the right list of signature requests.
- Create a predictable cue for reviewing agreement progress.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eversign to Notis once in the portal.
- 2Create an automation or ask Notis to list the relevant Eversign documents when the review page is updated.
- 3Describe which business and document status should be included in one instruction.
- 4Pick the Notion Page Content Updated trigger for the review page and choose a channel for run reports.
- 5Test with one real review update and confirm the returned document list is useful.
Questions about this workflow
Does this workflow change document status?
No. The Eversign action lists documents so you can review their status and follow up.
Can I make this check happen automatically every week?
This version starts when the Notion page changes. A recurring Notis schedule is another available trigger type.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eversign. A trigger fires from one place; an action lands in another.
Notion triggers
Eversign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Document Audit Log
Tool to retrieve the audit log for a document. use after obtaining the document hash to view its full event history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document
Tool to create a new document for signature. use after finalizing document details and signer list.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Template
Tool to create a new template. use when you need to programmatically set up reusable document templates after confirming your business settings.
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 or Template
Tool to delete a document or template by its hash. use when you need to permanently remove a document or template.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Bulk Jobs List
Tool to retrieve a list of bulk jobs for a business. use when you need to view or paginate existing bulk jobs.
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.
List Businesses
Tool to retrieve a list of businesses associated with your account. use when you need to fetch all businesses available to the authenticated user.
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.
List Documents
Tool to list documents for a business. use when you need to retrieve documents with optional filters after setting business id in query params.
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 Templates
Tool to list templates for a business with optional pagination. use when you need to retrieve a paginated list of templates.
Connect any two apps with Notis in the middle.
Notion and Eversign, 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 Eversign.