AppsPricingBlogTry it
Jira logo
Notion logo

Connect Jira to Notion

Use 4 documented Jira triggers to run 24 documented Notion actions.

4 source triggers
24 target actions
Reverse direction supported

Why Connect Jira & Notion?

Start with a Jira event

Choose from 4 documented triggers, including New Event, New Issue Created Event (Instant), New Issue Deleted Event (Instant).

Run a Notion action

Send the event into one of 24 documented actions, such as Append Block to Parent, Complete File Upload, Create Comment.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Jira logo

Jira

Triggers (4)

New Event

Emit new event when an event with subscribed event source triggered, See the documentation

webhook
New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

Notion logo

Notion

Triggers (9)

New Comment Created

Emit new event when a new comment is created in a page or block. See the documentation

polling
New Data Source Created

Emit new event when a data source is created. See the documentation

polling
New or Updated Page in Data Source (By Property)

Emit new event when a page is created or updated in the selected data source. See the documentation

polling
New or Updated Page in Data Source (By Timestamp)

Emit new event when a page is created or updated in the selected data source. See the documentation

polling
New Page in Data Source

Emit new event when a page is created in the selected data source. See the documentation

polling
New Webhook Event (Instant)

Emit new event each time a webhook event is received. Webhook must be setup in Notion. See the documentation

webhook
Page or Subpage Updated

Emit new event when the selected page or one of its sub-pages is updated. See the documentation

polling
Page Properties Updated (Instant)

Emit new event each time a page property is updated in a data source. For use with Page Properties Updated event type. Webhook must be set up in Notion. See the documentation

webhook
Page Updated

Emit new event when a selected page is updated. See the documentation

polling

Actions (24)

Append Block to Parent

Append new and/or existing blocks to the specified parent. See the documentation

Complete File Upload

Use this action to finalize a mode=multi_part file upload after all of the parts have been sent successfully. See the documentation

Create Comment

Create a comment in a page or existing discussion thread. See the documentation

Create Database

Create a database and its initial data source. See the documentation

Create File Upload

Create a file upload. See the documentation

Create Page

Create a page from a parent page. See the documentation

Create Page from Data Source

Create a page from a data source. See the documentation

Delete Block

Sets a Block object, including page blocks, to archived: true using the ID specified. See the documentation

Duplicate Page

Create a new page copied from an existing page block. See the documentation

Find Pages or Data Sources

Searches for a page or data source. See the documentation

Get Current User

Retrieve the Notion identity tied to the current OAuth token, returning the full users.retrieve payload for me (person or bot). Includes the user ID, name, avatar URL, type (person vs bot), and workspace ownership metadata—useful for confirming which workspace is connected, adapting downstream queries, or giving an LLM the context it needs about who is operating inside Notion. See the documentation.

List All Users

Returns all users in the workspace. See the documentation

List File Uploads

Use this action to list file uploads. See the documentation

Query Data Source

Query a data source with a specified filter. See the documentation

Retrieve Data Source Content

Get all content of a data source. See the documentation

Retrieve Data Source Schema

Get the property schema of a data source in Notion. See the documentation

Retrieve File Upload

Use this action to retrieve a file upload. See the documentation

Retrieve Page Content

Get page content as block objects or markdown. Blocks can be text, lists, media, a page, among others. See the documentation

Retrieve Page Metadata

Get details of a page. See the documentation

Retrieve Page Property Item

Get a Property Item object for a selected page and property. See the documentation

Retrieve User

Returns a user using the ID specified. See the documentation

Send File Upload

Send a file upload. See the documentation

Update Child Block

Updates a child block object. See the documentation

Update Data Source

Update a data source. See the documentation

Integration Features

4 documented Jira triggers
24 documented Notion actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Notion to Jira direction

Capability Examples

Jira trigger → Notion action

Catalog example
JiraJira

New Event

NotionNotion

Append Block to Parent

Notion trigger → Jira action

Reverse direction
NotionNotion

New Comment Created

JiraJira

Add Attachment To Issue

How It Works

1

Connect Apps

Authenticate your Jira and Notion accounts

2

Choose a Trigger

Select a documented Jira event

3

Choose an Action

Select the documented Notion operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented Jira triggers.

Automated Actions

Run one of 24 documented Notion actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Notion logoJira logo

Reverse Integration Available

Also connect Notion to Jira for bidirectional automation

View Integration
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations
Notion logo

All Notion Integrations

Explore all available Notion connections

View All Integrations

Ready to Connect Jira & Notion?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free