Keep Your Notion Status Fields in Sync with Jira
When an issue moves in Jira, its Notion counterpart moves too, in real time. No more hunting to check if something's actually done.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Update block
Updates an existing notion block's textual content or type-specific properties (e.g., 'checked' status, 'color'), using its `block id` and the specified `block type`.
Why this helps
You update a Jira issue status, forget to update Notion, and later act on outdated information. Your task lists become unreliable.
- Real-time alignment: Notion always reflects the current Jira status.
- Reduce mental model conflicts: stop carrying two separate views of project state.
- Trust your Notion dashboards: you know the status data is current.
- Less manual verification: no need to check Jira separately to confirm progress.
Setup
Build it in a few focused steps.
- 1Connect Jira and Notion to Notis once (portal or via any channel).
- 2Tell Notis: 'When a Jira issue status changes, update the status property in the matching Notion page.'
- 3Select the trigger: 'Updated Issue' (from your project).
- 4Pick your notification channel.
- 5Test by changing an issue status in Jira and verifying the Notion page updates within seconds.
Questions about this workflow
Does this work with custom Jira statuses?
Yes. Notis learns your Jira workflow statuses and maps them to your Notion status property values. Describe your mapping once, and it applies to all matched issues.
What if the Notion page doesn't exist yet?
This automation updates existing Notion pages. Pair it with the 'New Issue to Notion' automation to create pages first, then this keeps them synced.
Does this trigger on every field change, or just status?
This automation checks for status changes specifically. Other field updates (assignee, due date, etc.) won't trigger this unless you create separate automations.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Notion. A trigger fires from one place; an action lands in another.
Jira triggers
Notion actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Add multiple content blocks (bulk, user-friendly)
Efficiently adds multiple standard content blocks to a notion page in a single api call with automatic markdown parsing. the 'content' field in notionrichtext blocks now automatically detects and parses markdown formatting including headers (# ## ###), bold (**text**), italic (*text*), strikethrough (~~text~~), inline code (`code`), links ([text](url)), and more. ideal for bulk content creation, ai agents, and replacing multiple individual add page content calls. supports automatic text formatting, content splitting, and up to 100 blocks per request.
New Project
Triggered when a new project is added in Jira
Add content to Notion page
Deprecated: appends a single content block to a notion page or a parent block (must be page, toggle, to-do, bulleted/numbered list, callout, or quote); invoke repeatedly to add multiple blocks.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Append complex blocks (advanced, full control)
Appends complex blocks with full notion block structure to a parent block or page. use for advanced scenarios requiring precise control: code blocks, tables, embeds, nested children within blocks, or when working with pre-built notion block objects. requires full notion api block schema - use add multiple page content for simpler content creation.
Archive Notion Page
Archives (moves to trash) or unarchives (restores from trash) a specified notion page.
Create comment
Adds a comment to a notion page (via `parent page id`) or to an existing discussion thread (via `discussion id`); cannot create new discussion threads on specific blocks (inline comments).
Create Notion Database
Creates a new notion database as a subpage under a specified parent page with a defined properties schema; use this action exclusively for creating new databases.
Create Notion page
Creates a new empty page in a notion workspace.
Delete a block
Archives a notion block, page, or database using its id, which sets its 'archived' property to true (like moving to "trash" in the ui) and allows it to be restored later.
Connect any two apps with Notis in the middle.
Not just Jira and Notion. Any combination from 985+ 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 Notion.