Create a Jira issue from every new Notion database item
You capture ideas in Notion because it is fast and forgiving. But your team lives in Jira, and the handoff usually means re-typing everything by hand. Notis watches your Notion database and opens a matching Jira issue the second a new row appears, so the capture and the commitment stay in sync without you switching tabs.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Why this helps
Ideas captured in Notion never make it into Jira because copying each one over by hand is boring, easy to forget, and always slips to later.
- Every Notion item becomes a tracked Jira issue with zero re-typing
- The gap between capturing an idea and committing it to the backlog disappears
- You stop context-switching between Notion and Jira just to move one task across
Setup
Build it in a few focused steps.
- 1Connect Notion and Jira to Notis once from the portal.
- 2Ask Notis for your portal link, then open Automations and choose New Automation.
- 3Write the instruction in plain language, for example: When a new item is added to my Notion product database, create a matching Jira issue.
- 4Pick the New Page in a Notion database trigger and choose the channel where Notis should report each run.
- 5Add one real row in Notion to confirm the Jira issue appears as expected.
Questions about this workflow
Do I have to map Notion fields to Jira fields?
No. Notis reads your plain-language instruction and decides how to fill the Jira issue. There are no field-mapping screens to configure.
Which Notion database does it watch?
Whichever one you name in your instruction. Notis scopes the automation to the database you describe when you set it up.
What if I only want certain rows to become issues?
Just say so in the instruction, such as only rows marked ready for dev, and Notis applies that condition on each run.
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.