Skip to content
Notis

Start event promotion with available templates

When you log an event campaign, let Notis surface Imejis io templates that could support its promotion and keep planning on track.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

List Design Templates

Tool to list available design templates. Use after authenticating the account.

Why this helps

Event promotion combines many small asset decisions that are easy to postpone while managing logistics.

  • Connects campaign intake with visual planning.
  • Helps identify reusable options before promotion gets urgent.
  • Reduces one more manual search during event setup.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Imejis io to Notis once.
  • 2Create an automation in the portal and name it for event campaigns.
  • 3Write one plain-language prompt to list Imejis io templates when a new event campaign page is added.
  • 4Select New Page, choose the event campaign data source if useful, select a reporting channel, and test with one campaign.

Questions about this workflow

Does this trigger for new database rows?

Yes. New Page triggers when a new page is added to a Notion database.

Can the prompt distinguish promotional assets from logistics?

Ask Notis to use the campaign context and request templates only when the page indicates visual promotion needs.

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.

TriggerScheduled

List Design Templates

Tool to list available design templates. Use after authenticating the account.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

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.