Connect Notion to Docusign Developer

Use 9 documented Notion triggers to run 1 documented Docusign Developer actions.

9 source triggers

1 target actions

Reverse direction supported

Start Free Trial Browse Notion integrations

Why Connect Notion & Docusign Developer?

Start with a Notion event

Choose from 9 documented triggers, including New Comment Created, New Data Source Created, New or Updated Page in Data Source (By Property).

Run a Docusign Developer action

Send the event into one of 1 documented actions, such as Create Signature Request.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Notion

Triggers (9)

New Comment Created

Emit new event when a new comment is created in a page or block. See the documentation

polling

New Data Source Created

Emit new event when a data source is created. See the documentation

polling

New or Updated Page in Data Source (By Property)

Emit new event when a page is created or updated in the selected data source. See the documentation

polling

New or Updated Page in Data Source (By Timestamp)

Emit new event when a page is created or updated in the selected data source. See the documentation

polling

New Page in Data Source

Emit new event when a page is created in the selected data source. See the documentation

polling

New Webhook Event (Instant)

Emit new event each time a webhook event is received. Webhook must be setup in Notion. See the documentation

webhook

Page or Subpage Updated

Emit new event when the selected page or one of its sub-pages is updated. See the documentation

polling

Page Properties Updated (Instant)

Emit new event each time a page property is updated in a data source. For use with Page Properties Updated event type. Webhook must be set up in Notion. See the documentation

webhook

Page Updated

Emit new event when a selected page is updated. See the documentation

polling

Actions (24)

Append Block to Parent

Append new and/or existing blocks to the specified parent. See the documentation

Complete File Upload

Use this action to finalize a mode=multi_part file upload after all of the parts have been sent successfully. See the documentation

Create Comment

Create a comment in a page or existing discussion thread. See the documentation

Create Database

Create a database and its initial data source. See the documentation

Create File Upload

Create a file upload. See the documentation

Create Page

Create a page from a parent page. See the documentation

Create Page from Data Source

Create a page from a data source. See the documentation

Delete Block

Sets a Block object, including page blocks, to archived: true using the ID specified. See the documentation

Duplicate Page

Create a new page copied from an existing page block. See the documentation

Find Pages or Data Sources

Searches for a page or data source. See the documentation

Get Current User

Retrieve the Notion identity tied to the current OAuth token, returning the full users.retrieve payload for me (person or bot). Includes the user ID, name, avatar URL, type (person vs bot), and workspace ownership metadata—useful for confirming which workspace is connected, adapting downstream queries, or giving an LLM the context it needs about who is operating inside Notion. See the documentation.

List All Users

Returns all users in the workspace. See the documentation

List File Uploads

Use this action to list file uploads. See the documentation

Query Data Source

Query a data source with a specified filter. See the documentation

Retrieve Data Source Content

Get all content of a data source. See the documentation

Retrieve Data Source Schema

Get the property schema of a data source in Notion. See the documentation

Retrieve File Upload

Use this action to retrieve a file upload. See the documentation

Retrieve Page Content

Get page content as block objects or markdown. Blocks can be text, lists, media, a page, among others. See the documentation

Retrieve Page Metadata

Get details of a page. See the documentation

Retrieve Page Property Item

Get a Property Item object for a selected page and property. See the documentation

Retrieve User

Returns a user using the ID specified. See the documentation

Send File Upload

Send a file upload. See the documentation

Update Child Block

Updates a child block object. See the documentation

Update Data Source

Update a data source. See the documentation

Docusign Developer

Triggers (2)

New Change in Envelope Status

Emit new event when an envelope's status is updated

polling

New Folder

Emit new event when a new folder is created

polling

Actions (1)

Create Signature Request

Creates a signature request from a template See the documentation

Integration Features

9 documented Notion triggers

1 documented Docusign Developer actions

Configurable field mapping

Conditional workflow steps

Execution monitoring

A supported Docusign Developer to Notion direction

Capability Examples

Notion trigger → Docusign Developer action

Catalog example

Notion

New Comment Created

Docusign Developer

Create Signature Request

Docusign Developer trigger → Notion action

Reverse direction

Docusign Developer

New Change in Envelope Status

Notion

Append Block to Parent

How It Works

Connect Apps

Authenticate your Notion and Docusign Developer accounts

Choose a Trigger

Select a documented Notion event

Choose an Action

Select the documented Docusign Developer operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 9 documented Notion triggers.

Automated Actions

Run one of 1 documented Docusign Developer actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Reverse Integration Available

Also connect Docusign Developer to Notion for bidirectional automation

View Integration

All Notion Integrations

Explore all available Notion connections

View All Integrations

All Docusign Developer Integrations

Explore all available Docusign Developer connections

View All Integrations

Popular Integrations

View all integrations →

More Docusign Developer Integrations

View all Docusign Developer integrations →

Ready to Connect Notion & Docusign Developer?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free

Connect Notion to Docusign Developer

Why Connect Notion & Docusign Developer?

Start with a Notion event

Run a Docusign Developer action

Map and review the workflow

Available Triggers & Actions

Notion

Triggers (9)

Actions (24)

Docusign Developer

Triggers (2)

Actions (1)

Integration Features

Capability Examples

Notion trigger → Docusign Developer action

Docusign Developer trigger → Notion action

How It Works

Connect Apps

Choose a Trigger

Choose an Action

Test and Review

Frequently Asked Questions

Is the Notion to Docusign Developer direction supported?

Which Notion triggers are available?

Which Docusign Developer actions are available?

Can I also connect Docusign Developer to Notion?

Integration Benefits

Trigger-driven Workflows

Automated Actions

Provider Authentication

Guided Configuration

Field Mapping

Execution Review

Reverse Integration Available

All Notion Integrations

All Docusign Developer Integrations

Popular Integrations

More Docusign Developer Integrations

Ready to Connect Notion & Docusign Developer?