Connect Jira to Dynamics365

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

View example

Turn Jira support issues into Dynamics cases

Create a Dynamics case when a support issue is created in the configured Jira project.

View example

Turn Jira partner requests into Dynamics leads

Create a Dynamics lead from each new partner request issue in the configured Jira project.

View example

Track Jira expansion requests as Dynamics opportunities

Create a Dynamics opportunity when a new issue records an existing customer's expansion request.

View example

Reflect Jira issue changes in Dynamics cases

Use updates to linked Jira issues as a cue to update the corresponding Dynamics case.

View example

Keep Dynamics leads current from Jira sales request updates

Update the matching Dynamics lead when an existing Jira sales request issue changes.

View example

Add a Dynamics account when a Jira client project starts

Create a Dynamics account when a new Jira project represents a new client account.

View example

Update a Dynamics opportunity from Jira renewal signals

Update a linked Dynamics opportunity when a new Jira issue records a renewal signal.

View example

Create Dynamics leads from qualified intake webhooks

Create a Dynamics lead when an HTTP request sends Notis a qualified prospect intake.

Supported Triggers and Actions

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

Jira triggers

Dynamics365 actions

Recurring trigger

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

TriggerScheduled

Get all invoices action

ActionInstant

Webhook trigger

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

TriggerInstant

Create Account

Creates a new account entity record in dynamics crm using the web api.

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

Create Case

Creates a new case (incident) entity record in dynamics crm using the web api.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Create Contact

Creates a new contact entity record in dynamics crm using the web api.

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

Create Invoice

Creates a new invoice entity record in dynamics crm using the web api.

ActionInstant

Create Lead

Creates a new lead entity record in dynamics crm using the web api.

ActionInstant

Create Opportunity

Creates a new opportunity entity record in dynamics crm using the web api.

ActionInstant

Create Sales Order

Creates a new sales order entity record in dynamics crm using the web api.

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.