Route agreement emails with Notion context
Keep agreement correspondence aligned with the right team inbox when an envelope needs a specific reply or archive route.
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
Addemailoverridestoenvelope
Adds or modifies email override settings for a specific docusign envelope, allowing customization of the reply-to email address and name, as well as bcc email addresses for archiving purposes. this endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. it's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. note that these changes only affect email communications that occur after the addition is made, and the bcc feature is limited to users with appropriate permissions. for security reasons, additional signer authentication is recommended when using the bcc for email archive feature.
Why this helps
Envelope emails can reach the wrong inbox or miss an intended archive when their communication settings are handled separately.
- Apply agreement-specific reply-to details when needed.
- Support a consistent archive path for eligible envelopes.
- Reduce manual editing of envelope email settings.
Setup
Build it in a few focused steps.
- 1Connect Notion and DocuSign to Notis once.
- 2Create an automation prompt describing when to apply reply-to or archive overrides to an existing envelope and the approved settings to use.
- 3Select Notion Page Properties Updated and scope it to the agreement database if available.
- 4Choose a run-report channel and test with one real envelope where the override is appropriate.
Questions about this workflow
Does BCC archiving require special permissions?
The action description notes that BCC use is limited to users with appropriate permissions.
Will this create an envelope?
No. It modifies email settings for a specific existing envelope.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docusign. A trigger fires from one place; an action lands in another.
Notion triggers
Docusign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add contacts to contacts list
Adds multiple contacts to a user's contacts list in docusign. this endpoint allows for bulk addition of contacts with detailed information, including cloud provider details, phone numbers, email addresses, and notary-specific information. it's particularly useful for populating a user's address book efficiently or synchronizing contacts from external sources. the endpoint supports various contact types, including regular contacts, shared contacts, and signing groups. use this when you need to add or update multiple contacts simultaneously in a docusign account. note that while it can handle a variety of contact information, it does not provide functionality for removing or deactivating contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Addemailoverridestoenvelope
Adds or modifies email override settings for a specific docusign envelope, allowing customization of the reply-to email address and name, as well as bcc email addresses for archiving purposes. this endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. it's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. note that these changes only affect email communications that occur after the addition is made, and the bcc feature is limited to users with appropriate permissions. for security reasons, additional signer authentication is recommended when using the bcc for email archive feature.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add envelope attachments
Adds one or more envelope attachments to a draft or in-process envelope in docusign. this endpoint allows developers to include additional files with an envelope that are not converted to pdf and are only accessible through the api. it's useful for attaching supporting documents or metadata files that should not be part of the main signing process. the endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 mb each. note that these attachments are not visible in the docusign web application and are intended for programmatic use only.
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.
Add existing brand to group
This endpoint adds one or more existing brands to a specified group in docusign. it allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. the endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. it's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Addfiletoworkspace
This endpoint adds a file to a specific folder within a docusign workspace. it allows users to upload and organize files in their docusign account, enabling better document management and collaboration. the method should be used when integrating file upload functionality with docusign workspaces, such as when adding new documents to a project or sharing files with team members. it's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.
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.
Add members to signing group
This endpoint adds one or more new members to a specified signing group within a docusign account. signing groups allow multiple users to act as potential signers for a document, where any member of the group can sign on behalf of the group. this tool should be used when you need to expand or update the membership of an existing signing group. the endpoint allows you to add up to 50 members to a signing group, which is the maximum limit. when adding members, you must provide their email addresses and usernames. it's important to note that docusign recommends separating signer recipients and non-signer recipients (such as carbon copy recipients) into different signing groups to maintain clarity in the signing process.
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.
Add new users to a specified account
This endpoint adds new users to a specified docusign account, allowing bulk creation of up to 500 users in a single call. it's ideal for quickly setting up multiple users with customized permissions and settings. the endpoint requires at least a username and email for each user, but supports additional configuration options. it returns detailed information about created users, including ids and status.
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.
Addorupdateaccountstamps
This endpoint allows you to add or update one or more account stamps in a docusign account. it provides a comprehensive way to manage signature and stamp settings, including image properties, user associations, and stamp-specific details. use this endpoint when you need to create new stamps or modify existing ones for an account. it's particularly useful for bulk operations on multiple stamps. note that this endpoint doesn't handle the actual process of signing documents, but rather manages the stamps available for use in the signing process.
Connect any two apps with Notis in the middle.
Notion and Docusign, 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 Docusign.