Link Jira issues when a related Notion item is added
Dependencies are easy to spot when you write them into a Notion item and painfully easy to forget when it comes time to reflect them in Jira. Notis reads a new Notion item, finds the work it relates to, and links those Jira issues together, so blockers and connections are visible on the board instead of only in your head.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Link Issues
Links two jira issues using a specified link type with optional comment.
Why this helps
You note that two pieces of work depend on each other in Notion, but Jira never shows the link, so the dependency ambushes you later.
- Dependencies you note in Notion become real links on the Jira board
- Blockers surface early instead of ambushing a sprint mid-flight
- You stop manually wiring related tickets together after the fact
Setup
Build it in a few focused steps.
- 1Connect Notion and Jira to Notis one time in the portal.
- 2Open the portal link and start a New Automation.
- 3Write the instruction plainly, for example: When a new Notion item references related work, link the matching Jira issues together.
- 4Choose the New Page in a Notion database trigger and set your reporting channel.
- 5Add a Notion item that references another and confirm the Jira issues are linked.
Questions about this workflow
How does Notis know which issues to link?
It reads the references in your Notion item and matches them to Jira issues based on your instruction.
Can I choose the link type?
Yes. Say the relationship you want, such as blocks or relates to, and Notis applies that link type.
What if it cannot find a match?
Notis reports the miss to your channel so you can link it manually or refine the reference.
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.