Review Endorsal campaign details from Notion
Keep campaign requests in Notion and let Notis fetch the relevant Endorsal campaign details when a request arrives.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
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.
Why this helps
A campaign request can stall while someone searches for the correct Endorsal campaign and confirms its details.
- Bring campaign context into the request follow-up.
- Reduce time spent locating campaign information.
- Make it easier to confirm the intended campaign before acting.
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 to retrieve a campaign when a campaign request is added.
- 3Choose the Notion New Page trigger for the campaign request database.
- 4Choose a run-report channel and test with one real request that identifies an Endorsal campaign.
Questions about this workflow
What does this action retrieve?
It retrieves a specific autorequest campaign using its unique identifier.
Can it create or send a campaign?
This action only retrieves campaign details. It does not create or send a campaign.
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.