Move approved Notion quotes into Endorsal
Make approval the handoff point: once a quote is marked ready in Notion, Notis can submit it to Endorsal.
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
Create Testimonial
Tool to submit a new testimonial. use when adding customer feedback to your endorsal account after gathering input.
Why this helps
Approved quotes still need a second round of attention before they become usable social proof.
- Make approval a clear signal to proceed.
- Avoid repeatedly checking which quotes are ready.
- Keep the original customer context close to the testimonial.
Setup
Build it in a few focused steps.
- 1Connect Notion and Endorsal to Notis once in the portal.
- 2Create an automation in the portal or ask Notis for the approval-to-testimonial outcome.
- 3Choose the Notion Page Properties Updated trigger for the relevant records.
- 4Choose a run-report channel and test by approving one real quote.
Questions about this workflow
How does Notis know a quote is approved?
State the approval condition in the automation prompt, using the status or other context present in the Notion page.
Will every property change create a testimonial?
Tell Notis to act only when the record reaches the approved state and contains customer feedback suitable for submission.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Endorsal. A trigger fires from one place; an action lands in another.
Notion triggers
Endorsal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Testimonial
Tool to submit a new testimonial. use when adding customer feedback to your endorsal account after gathering input.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get AutoRequest Campaign
Tool to retrieve a specific autorequest campaign by its unique identifier. use when you need to fetch details of an existing autorequest campaign.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Contact
Tool to retrieve details of a specific contact by its unique identifier. use when you have the contact id and need to fetch complete contact details.
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.
Get Tag
Tool to retrieve details of a specific tag by its unique identifier. use when you have a tag id and need full tag metadata.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Testimonial
Tool to retrieve details of a specific testimonial by its unique identifier. use after obtaining the testimonial id to fetch its full details.
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.
Get Widget
Tool to retrieve details of a specific widget by its unique identifier. use when you need full widget details before editing or analysis.
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 AutoRequest Campaigns
Tool to retrieve a list of all autorequest campaigns. use when you need to view both active and inactive campaigns.
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 Contacts
Tool to retrieve all contacts associated with your account. use when you need to browse or manage your contact list after authentication.
Connect any two apps with Notis in the middle.
Notion and Endorsal, 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 Endorsal.