Connect Jira to Clickmeeting

When something happens in Jira, Notis takes the next step in Clickmeeting. 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 Clickmeeting

View example

Turn new Jira feature requests into customer webinars

Create a ClickMeeting webinar when a new Jira issue calls for a customer walkthrough, demo, or training session.

View example

Invite customers when a Jira release webinar is ready

When a Jira issue update marks a release webinar ready, send ClickMeeting invitations to the provided attendee list.

View example

Add Jira project owners as ClickMeeting contacts

When a new Jira project is created, use stated owner or presenter contact details to add a ClickMeeting contact for project onboarding.

Supported Triggers and Actions

Notis builds workflows that link Jira to Clickmeeting. A trigger fires from one place; an action lands in another.

Jira triggers

Clickmeeting actions

Recurring trigger

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

TriggerScheduled

Create Conference

Tool to create a new conference. use when you need to schedule or start a meeting/webinar after authentication.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Tool to create a new contact in your clickmeeting account. use when you need to add or pre-register an attendee before scheduling an 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

Delete Conference

Tool to delete a specific conference. use after confirming the conference is no longer needed.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Recording

Tool to delete a specific recording for a conference room. use when you need to remove an unwanted or outdated recording after confirming the conference and recording ids. deletion is irreversible.

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

Delete Recordings

Tool to delete all recordings for a conference room. use when you need to clear all saved recordings for a specific conference before archiving or reusing it.

ActionInstant

Generate Autologin URL

Tool to generate an autologin url for a conference participant. use when you need to provide direct access to a conference room without separate login.

ActionInstant

Generate Session PDF Report

Tool to generate a pdf report for a specific session. use when you need to download session analytics as a pdf file.

ActionInstant

Get Chat Details

Tool to retrieve details of a specific chat session. use when you have the chat id and need its metadata and messages.

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.