See available Docuseal templates when an agreement is requested
Skip a separate library search. Let Notis bring the available Docuseal template options into the flow when a new agreement request appears.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Templates
Tool to retrieve a list of all templates. use when you need to browse available templates with optional filters before selection.
Why this helps
Searching through a template library interrupts the requester before they can decide what document to use.
- Brings template options to the moment they are needed.
- Reduces time spent browsing another tool.
- Helps reveal when a standard template is already available.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docuseal to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to list available Docuseal templates for each new agreement request.
- 3Write one plain-language instruction explaining which request warrants a lookup and how Notis should report options.
- 4Select the Notion New Page trigger for the agreement requests database and choose a channel for run reports.
- 5Test with one request and confirm the template list is useful and current.
Questions about this workflow
Does the workflow select a template automatically?
No. It lists templates so a person can review the options and choose the appropriate one.
Can the list be narrowed?
Describe a relevant document type in the prompt. The action supports optional filters, but the automation is configured through plain-language instructions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docuseal. A trigger fires from one place; an action lands in another.
Notion triggers
Docuseal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Template
Tool to archive a specific template by its unique identifier. use after verifying the template id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clone Template
Tool to clone an existing template by its id with a new name. use after you have the template id and desired name to duplicate it into the same or a different folder.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Submission From PDF
Tool to create a one-off submission from a pdf file. use when you need to upload a pdf and initiate a signature workflow with optional custom field values and webhook notifications.
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 Template from HTML
Tool to create a template from html content. use when you need to define a reusable document template directly from html input.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Template
Tool to retrieve details of a specific template by its unique identifier. use when you need to fetch template metadata by id.
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 Submissions
Tool to list all document submissions with optional pagination and document filtering. use when you need to retrieve and browse existing submissions.
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 Submitters
Tool to retrieve a list of all submitters. use when you need a roster of submitters for reporting or management.
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 retrieve a list of all templates. use when you need to browse available templates with optional filters before selection.
Connect any two apps with Notis in the middle.
Notion and Docuseal, 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 Docuseal.