Add Loomio poll context to a Notion page discussion
A comment on a decision page can trigger a poll lookup, giving the discussion a shared reference point.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
SHOW_POLL
Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.
Why this helps
Page discussions lose momentum when people have to search separately for the decision poll.
- Keep discussion tied to the poll it concerns.
- Reduce repeat searching across tools.
- Give commenters a useful status snapshot in the run report.
Setup
Build it in a few focused steps.
- 1Connect Notion and Loomio to Notis once through the portal.
- 2Create an automation in the portal, or tell Notis to retrieve the related Loomio poll when a comment appears on a decision page.
- 3Describe in one plain-language instruction how Notis should identify the poll and report its details.
- 4Select the Notion New Comment trigger and scope it to the relevant page or block if desired.
- 5Choose a run-report channel and test with one real comment.
Questions about this workflow
How is this different from a workspace-wide comment trigger?
New Comment is designed for a specified Notion block or page, while Comment Created can cover workspace comments.
Can the poll be updated from the comment?
No. The available Loomio action retrieves poll details only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Loomio. A trigger fires from one place; an action lands in another.
Notion triggers
Loomio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Groups
Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Polls
Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Show Group
Tool to retrieve details of a specific group. use when you have a group id and need its full metadata.
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.
SHOW_POLL
Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.
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 Loomio, 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 Loomio.