Keep Demio session dates visible in Jira planning
A scheduled review can bring Demio session dates back into view and summarize them alongside the Jira planning context you provide.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Event Dates
Tool to list all scheduled session dates for a given Demio event. Use when you need the session schedule by event ID.
Why this helps
Session dates and project plans can drift apart when no one remembers to check both tools.
- Create a regular point to review scheduled sessions.
- Highlight dates that may need attention in the Jira context provided.
- Reduce reliance on remembering to check Demio manually.
Setup
Build it in a few focused steps.
- 1Connect Jira and Demio once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve Demio event dates and summarize them against the Jira planning context available to it, noting any missing context.
- 4Pick a recurring schedule as the trigger and choose where run reports go.
- 5Test with one real run and review whether the report includes the context you need.
Questions about this workflow
Does this automatically compare every Jira issue?
The available Demio action retrieves dates by event ID. The prompt needs access to relevant Jira context or event IDs; the schedule alone does not define which Jira issues to search.
Can it determine whether a date conflicts with a Jira deadline?
Only when the relevant Jira deadline and Demio date are available in the run context. Otherwise, Notis should report the missing information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Demio. A trigger fires from one place; an action lands in another.
Jira triggers
Demio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Demio Create Join Link
Tool to register an attendee and obtain their unique Demio join link. Use after confirming a valid event_id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Demio: Get Event by ID
Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Event Date Participants
Tool to list participants for a specific event date. Use after scheduling an event session to retrieve attendees.
New Project
Triggered when a new project is added in Jira
List Event Dates
Tool to list all scheduled session dates for a given Demio event. Use when you need the session schedule by event ID.
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.
List Demio Events
Tool to retrieve a list of Demio events. Use when you need to fetch events optionally filtered by type or paginated.
Demio API Ping
Tool to perform a health check on the Demio API. Use to verify the API is reachable before other calls.
Connect any two apps with Notis in the middle.
Jira and Demio, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Demio.