Post a Jira comment when a specific Notion page gets a comment
Some pages are the beating heart of a project, and their comment threads are full of decisions your engineers should see. Notis watches the specific Notion page or block you choose and relays each new comment onto the linked Jira issue, so the conversation follows the work instead of splintering across two tools.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Why this helps
The comment thread on your key Notion page holds the real decisions, but the team in Jira only sees a lonely ticket with none of that discussion.
- Decisions in a key page's thread reach the Jira issue automatically
- The team works from the full conversation, not a stripped-down ticket
- You avoid re-summarizing the same thread in a second tool
Setup
Build it in a few focused steps.
- 1Connect Notion and Jira to Notis once in the portal.
- 2Open your portal link and start a New Automation.
- 3Describe the outcome plainly, for example: When a new comment is added to this Notion page, post it on the linked Jira issue.
- 4Choose the New Comment trigger and name the page or block, then set your run-report channel.
- 5Add a comment to that page and confirm it appears on the Jira issue.
Questions about this workflow
How is this different from watching all comments?
This trigger focuses on a specific page or block you name, so only that thread relays to Jira rather than every comment in the workspace.
Can it include who commented?
Yes, ask for that in your instruction and Notis adds the author to the Jira comment.
Does it need special Notion permissions?
Comment events require the read comments capability, so re-authorize the connection once if it predates that setting.
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.