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 Jira and Salesforce See reverse direction

Trigger app

Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →

Action app

Salesforce as the action

Workflows do something in Salesforce, instantly.

See all 13 actions →

Both directions

Pick the way that fits your stack.

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

Jira → Salesforce

When something happens in Jira, do it in Salesforce.

6 Jira triggers wired to 13 Salesforce actions. Most-used pairing: Comment Created → Convert Lead.

Salesforce → Jira

Or fire it the other way around.

0 Salesforce triggers wired to 17 Jira actions downstream.

Use any trigger in the catalog as the upstream.

See Salesforce → Jira →

Popular pairings

Common Jira → Salesforce workflows.

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

Showing 9 of 78 combinations

When comment created in Jira, convert lead in Salesforce.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create account in Salesforce.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create contact in Salesforce.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create note in Salesforce.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When new issue in Jira, convert lead in Salesforce.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create account in Salesforce.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create contact in Salesforce.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create note in Salesforce.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When issue deleted in Jira, convert lead in Salesforce.

Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.

How it works

Connect Jira and Salesforce in five steps.

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

1
Connect
Authorize Jira and Salesforce
Open Tiny Command, authorize Jira and Salesforce once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Jira trigger
Drop the Jira → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/jira.trigger-comment-created
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 Salesforce action
Drop the Salesforce → Convert Lead action below it. Map fields from the Jira payload into the Salesforce inputs.
salesforce.convert-lead
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 Jira + Salesforce.

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 Jira.

Spreadsheets & Databases

Wire Jira to Salesforce in 2 minutes.

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

Try for free Request a demo

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

Pick the way that fits your stack.

When something happens in Jira, do it in Salesforce.

Or fire it the other way around.

Common Jira → Salesforce workflows.

Connect Jira and Salesforce in five steps.

Questions about Jira + Salesforce.

Other apps that pair well with Jira.

Wire Jira to Salesforce in 2 minutes.

Be the first to know what's next.