Per-pair page

Jira + Salesforce: feature requests and shipping milestones in CRM.

Create Jira issues from Salesforce customer requests, mirror release events back into Salesforce as Opportunity activity, or surface engineering signal to sales teams.

Connect Salesforce and Jira See reverse direction

Trigger app

Salesforce as the trigger

Workflows fire when something happens in Salesforce.

Salesforce has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Jira as the action

Workflows do something in Jira, instantly.

See all 17 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Salesforce → Jira

When something happens in Salesforce, do it in Jira.

0 Salesforce triggers wired to 17 Jira actions.

Jira → Salesforce

Or fire it the other way around.

6 Jira triggers wired to 13 Salesforce actions downstream.

See Jira → Salesforce →

Popular pairings

Common Salesforce → Jira workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 0 of 0 combinations

How it works

Connect Salesforce and Jira in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Salesforce and Jira
Open Tiny Command, authorize Salesforce and Jira once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Salesforce trigger
Drop the Salesforce → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/salesforce.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Jira action
Drop the Jira → Add Comment action below it. Map fields from the Salesforce payload into the Jira inputs.
jira.add-comment
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Salesforce + Jira.

How do I create a Jira issue from a Salesforce customer request?

Salesforce Opportunity Updated where "Feature Requests" custom field changes → Jira Create Issue in product backlog with the requested feature + linked Opportunity URL.

Can I notify Salesforce when a customer-tagged Jira issue ships?

Yes. Jira Issue Closed with customer tag → look up matching Salesforce Opportunity → Salesforce Create Task "Feature shipped, follow up with customer" assigned to AE.

How do I track Jira issue resolution time per Salesforce account?

Tag Jira issues with Salesforce Account ID. On Issue Closed, compute resolution time and Salesforce Update Account with the metric. SLA tracking for enterprise customers.

Can I surface Jira release-cadence in Salesforce dashboards?

Yes. Push release count and shipped-feature count to a Salesforce custom object weekly. Build a dashboard showing "features shipped this quarter" alongside revenue metrics.

How do I avoid syncing internal-only Jira work to Salesforce?

Filter Jira triggers to specific projects (customer-facing only) or labels. Internal infra and refactor work skips Salesforce; sales doesn't need that signal.

Can I attach Jira PR links to Salesforce Opportunity?

Yes. After Jira Issue Closed + linked PR Merged → Salesforce Update Opportunity with custom URL field for traceability. Sales can show customers exactly what was built.

Other apps that pair well with Salesforce.

Salesforce + Gmail

Salesforce + Slack

Communication

Salesforce + Google Sheets

Spreadsheets & Databases

Wire Salesforce to Jira in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo