Per-pair page

Connect GitBook to Stripe in two minutes.

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

Connect GitBook to Stripe — start free See reverse direction

Trigger app

GitBook as the trigger

Workflows fire when something happens in GitBook.

GitBook 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 →

Both directions

Pick the way that fits your stack.

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

GitBook → Stripe

When something happens in GitBook, do it in Stripe.

0 GitBook triggers wired to 31 Stripe actions.

Stripe → GitBook

Or fire it the other way around.

10 Stripe triggers wired to 3 GitBook actions downstream.

See Stripe → GitBook →

How it works

Connect GitBook and Stripe in five steps.

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

1
Connect
Authorize GitBook and Stripe
Open TinyCommand, authorize GitBook and Stripe once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a GitBook trigger
Drop the GitBook → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/gitbook.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 Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the GitBook payload into the Stripe inputs.
stripe.cancel-subscription
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitBook + Stripe.

How long does it take to connect GitBook and Stripe on TinyCommand?

Under two minutes. Authorize GitBook and Stripe once each, drop the GitBook trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the GitBook ↔ Stripe integration real-time?

Yes. Both GitBook 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 GitBook 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 GitBook events can trigger a Stripe workflow?

Use TinyCommand's universal Webhook trigger to receive GitBook events, then run any of the 31 Stripe actions downstream.

Do I need a paid plan to use GitBook with Stripe?

No. There's a free tier that covers most GitBook+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 → GitBook instead?

Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/gitbook page with the reverse-direction triggers and actions.