Build a Monthly Log of Overdue Issues in Notion

First day of each month, Notis adds a row to your Notion database logging all overdue Jira issues. Track delays and patterns over time.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Notion logo

Action

Insert row database

Creates a new page (row) in a specified notion database.

Why this helps

You notice issues slipping, but by next month you've forgotten which ones missed deadlines. Without historical records, you can't spot patterns or improve estimates.

  • Historical records: months of overdue snapshots let you see if delays are getting worse or better.
  • Identify patterns: which team members, projects, or issue types consistently miss dates.
  • Improve estimates: data shows how far off your predictions typically are.
  • Early intervention: spotting repeat issues lets you adjust process proactively.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Notion to Notis.
  • 2Tell Notis: 'On the first day of each month, create a Notion database row logging all currently overdue Jira issues, including their title, assignee, and how many days overdue.'
  • 3Set the trigger: 'Recurring schedule' (monthly, first day, any time).
  • 4Choose your notification channel.
  • 5After the first run, review the Notion row to ensure the data matches what you see in Jira.

Questions about this workflow

What counts as 'overdue' in Jira?

Tell Notis your definition: 'Issues with a due date before today.' Notis calculates days overdue automatically.

What if there are no overdue issues?

Notis still creates the row with a count of zero. This is valuable too—it shows when your team is on track.

Can I drill down to see individual overdue issues?

The monthly row is a summary. For detailed lists, create a separate automation or manually run a Jira search. The monthly log tracks trends over time.

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 logo

Jira triggers

Notion logo

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