Start a new sales workspace with EspoCRM context
A new sales database can create another place to coordinate. Get EspoCRM's current metadata as a quick reference when the workspace appears.
Trigger
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.
Action
Get Metadata
Tool to retrieve metadata information from espocrm. use when you need to discover system configuration, user details, acl, and translations right after authentication.
Why this helps
Starting sales work across Notion and EspoCRM can mean interrupting setup to hunt for configuration and access context.
- Surfaces EspoCRM configuration context when a sales database is created.
- Gives the team one concise setup note to reference.
- Reduces the need to switch tools just to inspect CRM metadata.
Setup
Build it in a few focused steps.
- 1Connect Notion and EspoCRM to Notis once through the portal.
- 2In Automations, create an automation named CRM workspace readiness check.
- 3Use one plain-language prompt: when a new Notion database is created, retrieve EspoCRM metadata and summarize relevant configuration and access context for the team; do not create or update CRM records.
- 4Select the Notion Database Created trigger, choose a channel for run reports, and test by creating one real sales database.
Questions about this workflow
Does this automation create CRM records?
No. The available EspoCRM action retrieves metadata, so the automation reports configuration context without creating or changing records.
When does the Notion trigger run?
It runs when a new Notion database container is created. Adding a data source to an existing database is a separate event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Espocrm. A trigger fires from one place; an action lands in another.
Notion triggers
Espocrm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get App User
Tool to retrieve current user data including token, acl, and preferences. use after successful authentication to fetch session-specific profile.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Metadata
Tool to retrieve metadata information from espocrm. use when you need to discover system configuration, user details, acl, and translations right after authentication.
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 Espocrm, 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 Espocrm.