Give brand asset requests a ready place to start
A new request is a natural time to see which Imejis io templates are available, so the next visual decision feels smaller.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
List Design Templates
Tool to list available design templates. Use after authenticating the account.
Why this helps
Open-ended asset requests can stall while someone searches for a suitable format or starting design.
- Provides a concrete starting point for a new request.
- Shortens the gap between asking and exploring formats.
- Keeps template research tied to the request context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Imejis io to Notis once.
- 2Create a named automation for brand asset requests in the portal.
- 3Tell Notis in one prompt to list relevant Imejis io templates when a brand asset request page is created.
- 4Choose Page Created and the request data source if appropriate, set a run-report channel, and test with one real request.
Questions about this workflow
Can requests include multiple asset types?
Yes. The prompt can ask Notis to consider the requested asset types when listing available templates.
Will it assign the request to someone?
No. This workflow lists templates; assignment or record updates are outside the available Imejis io action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Imejis io. A trigger fires from one place; an action lands in another.
Notion triggers
Imejis io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Design Templates
Tool to list available design templates. Use after authenticating the account.
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 Imejis 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 Imejis io.