Per-pair page

GitHub + Salesforce: feature requests and shipping milestones in your CRM.

Push GitHub issue and release events into Salesforce so sales sees what's shipping, what's in flight, and which customer-requested features are landing.

Connect Salesforce and GitHub 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

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

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

Salesforce → GitHub

When something happens in Salesforce, do it in GitHub.

0 Salesforce triggers wired to 23 GitHub actions.

GitHub → Salesforce

Or fire it the other way around.

1 GitHub triggers wired to 13 Salesforce actions downstream.

New GitHub Event

See GitHub → Salesforce →

Popular pairings

Common Salesforce → GitHub 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 GitHub in five steps.

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

1
Connect
Authorize Salesforce and GitHub
Open Tiny Command, authorize Salesforce and GitHub 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 GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Salesforce payload into the GitHub inputs.
github.add-labels-to-issue
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 + GitHub.

How do I sync GitHub feature releases into Salesforce Opportunities?

GitHub Release Published with "customer-requested" tag → look up linked Salesforce Opportunities (via custom field "Requested Features") → Salesforce Create Note + Update Stage if appropriate. Sales follows up.

Can I track GitHub PR resolution time per Salesforce Opportunity?

Yes. Tag GitHub issues with the Opportunity ID. On Issue Closed, compute resolution time and Salesforce Update Opportunity with the metric. Useful for SLA tracking with enterprise customers.

How do I notify sales when a customer-tagged GitHub PR merges?

GitHub PR Merged with customer tag → Salesforce Find Account by tag value → Salesforce Create Task assigned to the account owner with "feature shipped, follow up with customer" as the subject.

Can I create GitHub issues from Salesforce Opportunity feature requests?

Yes. Salesforce Opportunity Updated where a "Requested Features" field changes → GitHub Create Issue with the requested feature description. Engineering sees customer-driven backlog without leaving GitHub.

How do I avoid syncing internal-only GitHub work into Salesforce?

Filter triggers to specific repos or labels (customer-facing). Internal infra and refactor work skips Salesforce entirely. Sales doesn't need that signal.

Can I roll up GitHub release frequency into a Salesforce custom dashboard?

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

Other apps that pair well with Salesforce.

Salesforce + Gmail

Salesforce + Slack

Communication

Salesforce + Google Sheets

Spreadsheets & Databases

Wire Salesforce to GitHub in 2 minutes.

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

Try for free Request a demo