Per-pair page

Connect Close to Stripe in two minutes.

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

Trigger app
Close as the trigger

Workflows fire when something happens in Close.

  • Close has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.
Action app
Stripe as the action

Workflows do something in Stripe, instantly.

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

Pick the way that fits your stack.

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

CloseStripe

When something happens in Close, do it in Stripe.

0 Close triggers wired to 31 Stripe actions.

    StripeClose

    Or fire it the other way around.

    10 Stripe triggers wired to 9 Close actions downstream.

    See StripeClose
    Popular pairings

    Common Close → Stripe 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 Close and Stripe in five steps.

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

    1. 1
      Connect
      Authorize Close and Stripe

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

    2. 2
      Trigger
      Pick a Close trigger

      Drop the Close → New event trigger onto the canvas. TinyCommand auto-registers the webhook.

      POST /v1/webhooks/close.event
    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 Close 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 Close + Stripe.

    How long does it take to connect Close and Stripe on TinyCommand?
    Under two minutes. Authorize Close and Stripe once each, drop the Close trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
    Is the Close ↔ Stripe integration real-time?
    Yes. Both Close 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 Close 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 Close events can trigger a Stripe workflow?
    Use TinyCommand's universal Webhook trigger to receive Close events, then run any of the 31 Stripe actions downstream.
    Do I need a paid plan to use Close with Stripe?
    No. There's a free tier that covers most Close+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 → Close instead?
    Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/close page with the reverse-direction triggers and actions.
    Related

    Other apps that pair well with Close.

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

    Connect Close to Stripe — start free