Skip to content
APer-pair page

Connect Autopilot to Stripe in two minutes.

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

A
Trigger app
Autopilot as the trigger

Workflows fire when something happens in Autopilot.

Action app
Stripe as the action

Workflows do something in Stripe, instantly.

See all 31 actions →
Both directions

Pick the way that fits your stack.

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

AAutopilotStripe

When something happens in Autopilot, do it in Stripe.

2 Autopilot triggers wired to 31 Stripe actions. Most-used pairing: Contact AddedCancel Subscription.

AStripeAutopilot

Or fire it the other way around.

10 Stripe triggers wired to 2 Autopilot actions downstream.

See StripeAutopilot
Popular pairings

Common Autopilot → Stripe workflows.

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

Showing 8 of 62 combinations
A
When contact added in Autopilot, cancel subscription in Stripe.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, create charge in Stripe.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, create checkout session in Stripe.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact added in Autopilot, create coupon in Stripe.

Fires when a new contact is added to Autopilot (now Ortto) from any source — manual create, CSV import, API write, or form submission. Payload includes the full contact with custom fields. The base hook for "new lead → fan out to slack/sheet/CRM" patterns.

A
When contact updated in Autopilot, cancel subscription in Stripe.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, create charge in Stripe.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, create checkout session in Stripe.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

A
When contact updated in Autopilot, create coupon in Stripe.

Fires on any field change including custom-attribute writes and journey-state transitions. For specific change types (e.g., only when plan_tier becomes enterprise), inspect the previous_values vs current_values diff in the payload.

How it works

Connect Autopilot and Stripe in five steps.

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

  1. 1
    Connect
    Authorize Autopilot and Stripe

    Open Tiny Command, authorize Autopilot and Stripe once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Autopilot trigger

    Drop the Autopilot → Contact Added trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/autopilot.trigger-contact-added
  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 Autopilot payload into the Stripe inputs.

    stripe.cancel-subscription
  5. 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 Autopilot + Stripe.

How long does it take to connect Autopilot and Stripe on Tiny Command?
Under two minutes. Authorize Autopilot and Stripe once each, drop the Autopilot trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Autopilot ↔ Stripe integration real-time?
Yes. Both Autopilot 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 Autopilot 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 Autopilot events can trigger a Stripe workflow?
Any of the 2 Autopilot triggers, including "Contact Added". Each fires in real time when the matching event happens in Autopilot.
Do I need a paid plan to use Autopilot with Stripe?
No. There's a free tier that covers most Autopilot+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 → Autopilot instead?
Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/autopilot page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Autopilot.


Wire Autopilot to Stripe in 2 minutes.

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