Deliver a daily Jira digest on a schedule
Digging through Jira right before standup to remember what moved is a recipe for a scattered start. Each morning, Notis runs a search across your Jira board and reports the state of play to your channel, so you walk in already knowing what shipped, what is stuck, and what needs a nudge without opening a single board.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Search Issues Using JQL (POST)
Searches for jira issues using jql via post request for complex queries; ideal for lengthy jql queries that might exceed url character limits
Why this helps
Every standup starts with you frantically scrolling Jira to reconstruct what changed, which eats your focus before the day even begins.
- You start standup already knowing what moved and what is stuck
- No more frantic Jira scrolling in the two minutes before the call
- The morning digest lands in your channel with zero effort
Setup
Build it in a few focused steps.
- 1Connect Jira to Notis once from the portal.
- 2Open your portal link and choose New Automation.
- 3Describe it plainly, for example: Every weekday at 8am, search my Jira board for open and recently changed issues and post a summary.
- 4Pick a recurring schedule as the trigger and set the channel where the digest should land.
- 5Run it once and confirm the digest arrives with the right issues.
Questions about this workflow
Can I control which issues appear?
Yes. Describe the filter in plain words, like in-progress issues assigned to my team, and Notis builds the search for you.
Where does the digest go?
To whatever channel you choose for run reports, such as Telegram, WhatsApp, or email.
What time can it run?
Any schedule you set, so you can have it ready right before your standup.
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.