Pair new planning spaces with visual options
A new view can mark a workflow taking shape. Ask Notis to list Imejis io templates that may support its visual deliverables.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List Design Templates
Tool to list available design templates. Use after authenticating the account.
Why this helps
Setting up a new planning view can leave related design resources undiscovered until work is underway.
- Adds a visual resource check to new workflow setup.
- Helps connect planning structure with asset needs.
- Offers an early cue to explore templates.
Setup
Build it in a few focused steps.
- 1Connect Notion and Imejis io to Notis once.
- 2Create a new automation in the portal and name it for planning-view setup.
- 3Write one prompt asking Notis to list Imejis io templates relevant to the new view's purpose.
- 4Select View Created, choose a reporting channel, and test by creating a view for a real visual workflow.
Questions about this workflow
Can the prompt account for view type?
Yes. The event includes the view type, and the prompt can ask Notis to consider it when listing templates.
Will it create the view or a graphic?
No. Notion creates the view; this workflow only requests a list of available Imejis io templates.
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.