Integrations · E-commerce & payments

Stripe in the conversation.

The payment infrastructure behind most modern checkouts and subscription billing. Connect it once and your copilot works with customers, charges, invoices, subscriptions, refunds and disputes without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Stripe

E-commerce & payments

01 · COPILOT

Ask for it in plain language. It does the Stripe part.

Copilot rides inside the inbox. With Stripe connected it reads customers, charges, invoices, subscriptions, refunds and disputes and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Find a customer by email and read their payment history
Look up a charge or payment intent and why it failed
Read an invoice and its status
Read a subscription — plan, period and cancellation state
Issue or look up a refund
Read an open dispute and its evidence deadline

What a specific connection exposes is decided by Stripe, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Stripe. A workflow starts.

Once Stripe is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

A payment succeeds or fails
An invoice is paid or becomes overdue
A subscription is created or cancelled

The picker is the authority on which events your Stripe connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Stripe tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Stripe said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Stripe tools you left enabled and nothing else.

What teams do with it

Two ways Stripe earns its connection.

"Why was I charged?" with the actual charge

Copilot pulls the charge, the date and the description into the thread so the agent answers with the line item instead of "let me check with billing".

Failed payment, human message

A workflow opens a conversation on a failed renewal — the card, the amount, and a link to fix it — before the customer notices the service stopped.

Setup

Connect Stripe in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Stripe in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Stripe from its card.
3
Authorize with your own Stripe account
You sign in on Stripe's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Stripe questions.

How do I connect Stripe to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Stripe. Connecting it opens Stripe's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.

What can Cloodot do in Stripe?

Work of this kind: find a customer by email and read their payment history; look up a charge or payment intent and why it failed; read an invoice and its status; read a subscription — plan, period and cancellation state; issue or look up a refund; read an open dispute and its evidence deadline. The exact list depends on what your Stripe account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Stripe tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Stripe connection is a matter of leaving the writes off.

Can an event in Stripe start a Cloodot workflow?

Yes. Events like a payment succeeds or fails, an invoice is paid or becomes overdue, a subscription is created or cancelled appear in the workflow editor's trigger picker once Stripe is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Stripe?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Stripe account that authorized it, so a e-commerce & payments connection is only ever as broad as the account behind it.

More e-commerce & payments