Keep contract revisions aligned across Notion and BoldSign
Capture the change once in Notion and ask Notis to carry the approved revision into the corresponding BoldSign document.
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
Edit Document (Beta)
Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
Why this helps
Terms can change during negotiation, and copying those changes across tools creates a risk of sending an outdated version.
- Reduce duplicate edits across contract tools.
- Keep revised terms tied to the decision record.
- Lower the chance of sending a stale draft.
Setup
Build it in a few focused steps.
- 1Connect Notion and BoldSign to Notis once in the portal.
- 2Create the automation in the portal or describe the task to Notis conversationally.
- 3Write one instruction asking Notis to update the corresponding BoldSign document when contract content changes and the page indicates the revision is approved.
- 4Select the Notion page content updated trigger and choose a channel for run reports.
- 5Test with one controlled revision and confirm the intended BoldSign document changed.
Questions about this workflow
Will every content edit change the document?
Use the instruction to have Notis act only on approved, meaningful changes. Test that condition before relying on it.
Can it edit documents that are already sent?
The action supports editing a draft or sent document. Whether a specific change is appropriate depends on the document's current status and settings.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Boldsign. A trigger fires from one place; an action lands in another.
Notion triggers
Boldsign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Brand Details
Tool to get brand details by brand ID. Use after obtaining the brand identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Brands
Tool to list all brands in the account. Use after confirming account is authenticated.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Custom Field
Tool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand.
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.
Edit Custom Field
Tool to edit an existing custom field. Use when you need to update a custom field's properties after creation.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Behalf Documents
Tool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others.
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.
Edit Document (Beta)
Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
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.
Extend Document Expiry
Tool to extend a document's expiry date. Use before signing to prolong a document's deadline.
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 My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Connect any two apps with Notis in the middle.
Notion and Boldsign, 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 Boldsign.