Find a creative starting point for every campaign brief
Add a campaign brief in Notion and get a current list of Imagior templates to consider before you begin designing.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List design templates
Tool to list all design templates. Use when you need to retrieve every template associated with your account.
Why this helps
Starting a campaign from a blank canvas adds another decision-heavy task to an already crowded founder's day.
- Avoid manually opening Imagior just to browse available templates.
- Keep campaign planning and creative discovery close together.
- Make the next design step easier to choose.
Setup
Build it in a few focused steps.
- 1Connect Notion and Imagior to Notis once in the portal.
- 2Create an automation in the portal, or tell Notis in plain language to list Imagior templates when a campaign brief is added in Notion.
- 3Pick the Notion New Page trigger and choose where Notis should report runs.
- 4Test it by adding one real campaign brief and reviewing the template list.
Questions about this workflow
Does this create a campaign image?
No. The available Imagior action lists design templates. Notis can use the new brief as context for the lookup, but image creation is not part of this workflow.
Can I use this for a database of campaign briefs?
Yes. Connect the integrations, then choose the New Page trigger and describe the campaign-brief use case in the automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Imagior. A trigger fires from one place; an action lands in another.
Notion triggers
Imagior actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List design templates
Tool to list all design templates. Use when you need to retrieve every template associated with your 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 Imagior, 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 Imagior.