Connect Jira to Demio

When something happens in Jira, Notis takes the next step in Demio. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Demio

View example

Match Jira Webinar Requests to Demio Events

When a Jira issue requests a webinar, find Demio events that could match it and summarize the options for review.

View example

Create a Demio Join Link from a Jira Attendee Request

For a Jira issue requesting webinar registration, register the attendee and return their unique Demio join link when a valid event ID is available.

View example

Check Demio Session Dates When a Jira Issue Changes

When a Jira issue changes, check the session dates for its referenced Demio event and summarize the schedule for the team.

View example

Review Demio Events When a Jira Project Starts

When a Jira project is created, list Demio events and prepare a concise catalog for the team to consider during project kickoff.

View example

Review Upcoming Demio Sessions Against Jira Plans

On a recurring schedule, review scheduled Demio dates and compare them with relevant Jira project or issue context supplied to Notis.

View example

Check Demio Connectivity Before Webinar Work

Use an HTTP webhook to run a Demio API health check before a planned Jira webinar operation and report whether the API responds.

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.

TriggerScheduled

Demio Create Join Link

Tool to register an attendee and obtain their unique Demio join link. Use after confirming a valid event_id.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Demio: Get Event by ID

Tool to retrieve event details by ID. Use when you need the full metadata for a specific Demio event.

ActionInstant

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

List Event Date Participants

Tool to list participants for a specific event date. Use after scheduling an event session to retrieve attendees.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

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

List Demio Events

Tool to retrieve a list of Demio events. Use when you need to fetch events optionally filtered by type or paginated.

ActionInstant

Demio API Ping

Tool to perform a health check on the Demio API. Use to verify the API is reachable before other calls.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.