Keep deal documents close to your sales playbook
When the sales playbook changes, Notis can show the Flexisign catalog so you can review the document options that support your process.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
List Templates
Tool to list all available document templates. use when you need to retrieve and display templates from your flexisign account after connecting.
Why this helps
Sales process improvements can be hard to apply consistently when supporting documents are hidden in another tool.
- Keep available templates close to the sales process reference.
- Reduce extra searches when refining deal steps.
- Make the document review easy to repeat.
Setup
Build it in a few focused steps.
- 1Connect Notion and Flexisign to Notis once through the portal.
- 2Create an automation in the portal or request it from Notis conversationally.
- 3Write one instruction asking Notis to list Flexisign templates when the specified sales playbook page changes.
- 4Choose the Notion Page Updated trigger for the playbook and pick a run-report channel.
- 5Test by making one real update to a playbook block.
Questions about this workflow
Is this intended to watch all sales pages?
The Page Updated trigger is for a specified page; choose the playbook page you want to monitor.
Can Notis choose the best template?
The supported action lists available templates. Review and choose one yourself.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Flexisign. A trigger fires from one place; an action lands in another.
Notion triggers
Flexisign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Templates
Tool to list all available document templates. use when you need to retrieve and display templates from your flexisign account after connecting.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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 Flexisign, 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 Flexisign.