Per-pair page

Connect Freshsales to Stripe in two minutes.

Real-time triggers from Freshsales, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.

Trigger app
Freshsales as the trigger

Workflows fire when something happens in Freshsales.

Action app
Stripe as the action

Workflows do something in Stripe, instantly.

See all 31 actions →
Connect Freshsales to Stripe — start free
Both directions

Pick the way that fits your stack.

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

FreshsalesStripe

When something happens in Freshsales, do it in Stripe.

4 Freshsales triggers wired to 31 Stripe actions. Most-used pairing: Freshsales Contact CreatedCancel Subscription.

StripeFreshsales

Or fire it the other way around.

10 Stripe triggers wired to 12 Freshsales actions downstream.

See StripeFreshsales
Popular pairings

Common Freshsales → Stripe workflows.

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

Showing 9 of 124 combinations
When freshsales contact created in Freshsales, cancel subscription in Stripe.

Fires when a new contact is added to the Freshsales CRM. The base hook for "new lead → enrichment + Slack ping + onboarding sequence" cross-app workflows.

When freshsales contact created in Freshsales, create charge in Stripe.

Fires when a new contact is added to the Freshsales CRM. The base hook for "new lead → enrichment + Slack ping + onboarding sequence" cross-app workflows.

When freshsales contact created in Freshsales, create checkout session in Stripe.

Fires when a new contact is added to the Freshsales CRM. The base hook for "new lead → enrichment + Slack ping + onboarding sequence" cross-app workflows.

When freshsales contact created in Freshsales, create coupon in Stripe.

Fires when a new contact is added to the Freshsales CRM. The base hook for "new lead → enrichment + Slack ping + onboarding sequence" cross-app workflows.

When freshsales contact updated in Freshsales, cancel subscription in Stripe.

Fires on any contact change. For specific transitions (lifecycle stage change, owner reassignment), filter the payload before downstream side-effects.

When freshsales contact updated in Freshsales, create charge in Stripe.

Fires on any contact change. For specific transitions (lifecycle stage change, owner reassignment), filter the payload before downstream side-effects.

When freshsales contact updated in Freshsales, create checkout session in Stripe.

Fires on any contact change. For specific transitions (lifecycle stage change, owner reassignment), filter the payload before downstream side-effects.

When freshsales contact updated in Freshsales, create coupon in Stripe.

Fires on any contact change. For specific transitions (lifecycle stage change, owner reassignment), filter the payload before downstream side-effects.

When freshsales deal created in Freshsales, cancel subscription in Stripe.

Fires on new deal creation. Payload includes value, stage, owner, contact. The pipeline-growth hook for revenue forecast updates and AE notifications.

How it works

Connect Freshsales and Stripe in five steps.

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

  1. 1
    Connect
    Authorize Freshsales and Stripe

    Open TinyCommand, authorize Freshsales and Stripe once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Freshsales trigger

    Drop the Freshsales → Freshsales Contact Created trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/freshsales.trigger-contact-created
  3. 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. 4
    Action
    Add the Stripe action

    Drop the Stripe → Cancel Subscription action below it. Map fields from the Freshsales payload into the Stripe inputs.

    stripe.cancel-subscription
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Freshsales + Stripe.

How long does it take to connect Freshsales and Stripe on TinyCommand?
Under two minutes. Authorize Freshsales and Stripe once each, drop the Freshsales trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Freshsales ↔ Stripe integration real-time?
Yes. Both Freshsales and Stripe expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Freshsales and Stripe?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Stripe.
What Freshsales events can trigger a Stripe workflow?
Any of the 4 Freshsales triggers, including "Freshsales Contact Created". Each fires in real time when the matching event happens in Freshsales.
Do I need a paid plan to use Freshsales with Stripe?
No. There's a free tier that covers most Freshsales+Stripe use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Stripe → Freshsales instead?
Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/freshsales page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Freshsales.

+
Freshsales + Gmail
Email
+
Freshsales + Slack
Communication
+
Freshsales + Google Sheets
Spreadsheets & Databases
+
Freshsales + HubSpot
CRM & Sales
+
Freshsales + Notion
Productivity
+
Freshsales + Airtable
Spreadsheets & Databases

Connect Freshsales to Stripe — start free