Send a Jira notification when a Notion comment flags a blocker
A blocker mentioned in a Notion comment can sit unseen for hours while work grinds on around it. Notis picks up that comment on your watched page and sends a notification on the linked Jira issue, so the people who can unblock it hear about it quickly instead of discovering it at the next standup.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Send Notification for Issue
Sends a customized email notification for a jira issue.
Why this helps
Someone flags a blocker in a Notion comment, but nobody in Jira notices until standup, and by then a full day is lost.
- Blockers raised in Notion reach the Jira team within minutes
- Work stops piling up behind a problem no one saw
- You react to issues in real time instead of at the next standup
Setup
Build it in a few focused steps.
- 1Connect Notion and Jira to Notis once in the portal.
- 2Open your portal link and choose New Automation.
- 3Write it plainly, for example: When a comment on this Notion page mentions a blocker, send a notification on the related Jira issue.
- 4Pick the New Comment trigger and name the page, then set your run-report channel.
- 5Add a test comment mentioning a blocker and confirm the Jira notification is sent.
Questions about this workflow
How does Notis decide it is a blocker?
It reads the comment against the condition you set in your instruction, such as mentioning blocked or stuck.
Who gets the notification?
Notis sends the Jira issue notification to the recipients you describe, such as the assignee and watchers.
Does it need comment permissions?
Yes, comment events require the read comments capability on the Notion connection, so re-authorize once if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Jira. A trigger fires from one place; an action lands in another.
Notion triggers
Jira actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Add Attachment
Uploads and attaches a file to a jira issue.
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.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
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.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
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.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
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.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Page
Triggers when a new page is added to a Notion database.
Link Issues
Links two jira issues using a specified link type with optional comment.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Notion and Jira. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.