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

Details

Auto-create Salesforce leads from new Jira issues

Turn every new Jira issue into a tracked sales prospect in Salesforce—no manual data entry.

Details

Create Salesforce tasks from Jira issue updates

Track every Jira issue progress as a follow-up task in Salesforce—stay accountable without manual logging.

Details

Create Salesforce accounts from new Jira projects

When you kick off a new Jira project, Notis creates a matching account in Salesforce—business relationships tracked from day one.

Details

Create Salesforce opportunities from new Jira issues

Track potential deals instantly by creating an opportunity in Salesforce every time a new issue signals revenue opportunity.

Details

Auto-route new Jira issues to Salesforce lead owners

When an issue signals a new prospect, Notis automatically applies lead assignment rules—no manual routing needed.

Details

Create Salesforce notes from Jira issue updates

Build a permanent audit trail: every Jira issue update automatically becomes a documented note in Salesforce.

Details

Add issue reporters to Salesforce campaigns automatically

Every new issue brings a contact—add them to your campaigns automatically so nobody falls through onboarding.

Details

Clone opportunities when Jira issues expand in scope

When an issue grows into multiple workstreams or phases, Notis clones the opportunity with fresh line items—deal value is captured accurately.

Details

Create Salesforce contacts from new Jira issue participants

Track every person involved in an issue—reporters, assignees, and stakeholders become contacts in Salesforce instantly.

Supported Triggers and Actions

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

Jira triggers

Salesforce actions

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 Salesforce Account

Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add contact to campaign

Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

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

Add lead to campaign

Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

ActionInstant

Add product to opportunity

Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.

ActionInstant

Apply lead assignment rules

Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.

ActionInstant

Associate contact to account

Associates a contact with an account by updating the contact's accountid field.

ActionInstant

Clone opportunity with products

Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.

ActionInstant

Clone record

Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.

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.