Connect Whatsapp and Jira to power automations.

Trigger from one app, act on another, with a thinking brain in the middle. Build it in plain English. Approve from your phone.

When this happens · Trigger

Do this · Action

Build an automation Browse templates

Popular workflows

Most used workflows for Whatsapp + Jira

Details

Create a Jira task from every WhatsApp message

Automatically create a tracked task in Jira when a customer messages you on WhatsApp

Details

Add WhatsApp messages as comments to existing Jira tickets

Automatically post customer WhatsApp messages as comments on related Jira issues

Details

Create a Jira issue when a customer taps an interactive button

Convert customer button selections on WhatsApp into structured Jira issues

Details

Automatically attach customer media from WhatsApp to Jira issues

Keep photos, documents, and files sent via WhatsApp attached to the related Jira ticket

Details

Auto-assign Jira issues based on WhatsApp message content

Automatically route incoming WhatsApp messages to the right team member by assigning related Jira issues

Details

Track WhatsApp message template approvals and rejections in Jira

Log every template status change as a comment in Jira for compliance and audit purposes

Details

Automatically add customers to watch related Jira issues

Let customers follow progress on their issues by automatically adding them as watchers on Jira tickets

Details

Automatically link related Jira issues when a customer messages

Connect related tickets automatically so your team sees dependencies and related work at a glance

Details

Find existing Jira issues before creating duplicates from WhatsApp

Check for related tickets automatically so you don't create duplicates when customers report known issues

Supported Triggers and Actions

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

Whatsapp triggers

Jira actions

Message Status Updated

Triggers when a WhatsApp message status changes. IMPORTANT LIMITATION: WhatsApp Cloud API does not provide a native polling endpoint for message status. Status updates are ONLY delivered via webhooks in real-time. This trigger cannot directly poll the WhatsApp API for status updates. This trigger will return empty results as WhatsApp does not support this operation. To track message status updates, you must: 1. Set up a webhook endpoint to receive status notifications from WhatsApp 2. Store the webhook data in your own database 3. Use a different mechanism to query your stored webhook data For more information, see: - https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

New Message Received

Triggered in real time when your WhatsApp Business number receives an inbound message from a customer (text, media, location, or contact). Delivered via the Cloud API webhook.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Interactive Reply Received

Triggered when a customer taps a quick-reply button or selects an option from an interactive list message you sent.

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Message Template Status Update

Triggered when the review status of a WhatsApp message template changes — for example approved, rejected, or flagged — on your WhatsApp Business Account.

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

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.