Connect Salesforce 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 Salesforce + Jira

Details

Auto-Create Jira Issues from New Salesforce Leads

Instantly create a tracked task in Jira whenever a new lead arrives in Salesforce, so nothing gets missed.

Details

Update Jira Issues When Salesforce Opportunities Change

Sync opportunity updates from Salesforce directly into your Jira issues so your team stays current without checking two dashboards.

Details

Assign Jira Issues Based on Salesforce Contact Changes

When a contact owner changes in Salesforce, automatically reassign related Jira tasks to the right team member.

Details

Create Jira Issues When New Salesforce Accounts Arrive

Each new account in Salesforce automatically spawns a tracked Jira issue so your team knows about it from day one.

Details

Transition Jira Issues When Salesforce Tasks Complete

Close Jira tasks automatically when the corresponding Salesforce task is marked done, keeping your board current without manual updates.

Details

Search Jira for Existing Work When New Salesforce Contacts Arrive

Check if there's already related work in Jira before creating duplicate issues from new Salesforce contacts.

Details

Add Comments to Jira Issues When Opportunities Change

Automatically post opportunity updates as comments in Jira so your team has a complete history without checking Salesforce.

Details

Find Jira Users When New Leads Arrive in Salesforce

Automatically look up the right Jira user by email when a new lead comes in, so you know who to assign work to.

Details

Bulk-Create Jira Issues from External Webhooks

Send data to Notis via webhook and instantly create multiple Jira issues in one go, perfect for batch imports or custom integrations.

Supported Triggers and Actions

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

Salesforce triggers

Jira actions

Account Created or Updated

Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Contact Updated

Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.

TriggerPolling

Add Comment

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

ActionInstant

Record Updated (Generic SObject)

Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.

TriggerPolling

Add Watcher to Issue

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

ActionInstant

New Contact Trigger

Triggers when a new Contact is Created in Salesforce.

TriggerPolling

Assign Issue

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

ActionInstant

New Lead Trigger

Triggers when a new Lead is created in Salesforce.

TriggerPolling

Bulk Create Issues

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

ActionInstant

New or Updated Opportunity

Triggers when a Salesforce Opportunity is created or updated.

TriggerPolling

Create Issue

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

ActionInstant

Task Created or Completed

Triggers when a Task is created or when its status changes to Completed in Salesforce. Supports optional filtering by task Status or Subject.

TriggerPolling

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.