Review your contract template inventory monthly
Keep reusable agreements visible with a small recurring check that does not depend on remembering to look.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Templates
Tool to retrieve a list of all templates. use when you need to browse available templates before selecting one.
Why this helps
As a business grows, forgotten or unfamiliar templates can make a simple contract task take longer than expected.
- Creates a regular moment to review available templates.
- Helps reduce last-minute searching for a suitable agreement.
- Keeps the review separate from the pressure of an active deal.
Setup
Build it in a few focused steps.
- 1Connect Notion and Esignatures.io to Notis once in the portal.
- 2Create a monthly scheduled automation that lists available contract templates.
- 3Describe the desired inventory summary in one plain-language instruction.
- 4Choose a monthly schedule and run-report channel, then test once.
Questions about this workflow
Can it delete outdated templates?
No. This workflow lists templates for review. Deleting a template requires a separate action and a specific template ID.
Why use a schedule for this workflow?
Template inventory is a periodic review, so a recurring Notis schedule is a natural trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Esignatures io. A trigger fires from one place; an action lands in another.
Notion triggers
Esignatures io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contract
Tool to create a new contract using a specified template and signer details. use after selecting a template when you need to send a contract for signature.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Signer
Tool to create a new signer profile. use when you need to add a signer to an existing signature request.
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 want to register a reusable contract template after defining document elements.
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 Template
Tool to delete a specific template by its id. use when you need to remove an unused or outdated template after confirming its id.
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 id. use when you need to fetch a template’s metadata after selecting its 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 Templates
Tool to retrieve a list of all templates. use when you need to browse available templates before selecting one.
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.
Withdraw Contract
Tool to withdraw a contract by its id. use when you need to prevent further signing of a contract that hasn't been fully signed.
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.
Connect any two apps with Notis in the middle.
Notion and Esignatures io, 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 Esignatures io.