Skip to content
Notis

Every Feature Request Feeds Your Notion Roadmap

New feature requests in Jira automatically append to your Notion roadmap page. You're building a living product ideas log without manual work.

Trigger

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

Action

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.

Why this helps

Feature requests pour into Jira, but your Notion product roadmap stays stale. You end up with disconnected feature lists and miss emerging patterns in customer asks.

  • Centralized feedback: all feature requests feed into one Notion page.
  • Emergent patterns: a growing list makes common asks obvious.
  • Product thinking: see feature volume and theme changes over time.
  • Stakeholder visibility: product roadmap pages stay current and comprehensive.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Notion to Notis.
  • 2Tell Notis: 'Whenever a new feature request is created in Jira, append the title, description, and requested by to my Product Roadmap page in Notion.'
  • 3Set the trigger: 'New Issue' (filter for feature request issue type if your Jira uses them).
  • 4Choose your notification channel.
  • 5Create a test feature request in Jira and verify it appears as a content block in your Notion page within seconds.

Questions about this workflow

Should all new issues get added or just feature requests?

Tell Notis to check the issue type. For example: 'Only add issues if type is Feature Request.' Notis filters automatically.

Can I customize the content block format?

Yes. Describe the format: 'Include the title as a heading, description, priority, and requester name.' Notis structures the blocks accordingly.

What if my Notion roadmap page gets huge?

This automation appends to one page. Once it's large, you can manually archive old entries or organize them into subpages. Consider creating separate automations for different product areas.

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.

TriggerInstant

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.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

Archive Notion Page

Archives (moves to trash) or unarchives (restores from trash) a specified notion page.

ActionInstant

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).

ActionInstant

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.

ActionInstant

Create Notion page

Creates a new empty page in a notion workspace.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Jira and Notion. 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 Notion.