Apps › Payments

Stripe automation with Bizomate

When a Stripe payment succeeds, someone sends a receipt and updates the books; when one fails, someone needs to know today. Bizomate does both the moment Stripe reports it, and makes customers, payment links, checkout pages and invoices for you. Refunds are marked as steps that move money, and every run leaves a record you can read.

Start free

On every plan, Free included.

At a glance

Label	Value
Plans	Every plan
Connect	A secret or restricted key
Starts runs	Instantly
Kind	Connected app · Payments

What can start a workflow

Payment succeeded
When a payment succeeds

Publishing makes a webhook endpoint in your Stripe account for the trigger's event, in the key's mode, test or live; there is nothing to paste. Every event's signature is checked, and one that does not match starts nothing.

Payment failed
When a customer's payment fails

Checkout completed
When a customer finishes Stripe Checkout

Invoice paid
When an invoice is paid

Subscription created
When a customer starts a subscription

Subscription cancelled
When a subscription ends

Charge refunded
When a charge is refunded, in full or part

New customer
When a customer is created in Stripe

What a workflow can do with it

Create a customer
A customer in Stripe

Find a customer
Looks a customer up by email

By email. Nobody found takes the When nothing is found path, not a failed step.

Create a payment link
A link the customer pays by, for a price or an amount

For a price from Stripe, or for an amount and a product name.

Create an invoice
An invoice with items, sent to the customer to pay

Sent to the customer unless you switch off Send it; then it stays a draft in Stripe.

Create a refund
Sends money back for a payment — all of it, or part

Moves money: all of a payment, or part. A retry of the step sends the same idempotency key, so the customer is refunded once, and a test run with a live key asks first.

Retrieve a charge or payment
A charge's or payment intent's status and amount

Create a checkout session
A Stripe Checkout page for one price or amount

Cancel a subscription
Ends a subscription now, or when its period ends

At the end of the period unless you switch that off; then it ends now.

How you connect it

Paste a secret key from the Stripe Dashboard, under Developers › API keys — or a restricted key that can do only what you allow. Test keys (sk_test_, rk_test_) never move real money, and a connection with one shows a Test mode pill wherever it is used. Bizomate tests the key before saving it, and Test answers "Reached Stripe · test mode" or "Reached Stripe · live". A restricted key used with triggers needs Webhook Endpoints write. Stripe charges its own fees on each payment.

The key is encrypted before it is saved, used only when a step runs or a test calls Stripe, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect Stripe, Start a workflow from Stripe payment events, Create a Stripe payment link or checkout session, Refund or retrieve a Stripe payment and Steps that move money.

Questions about Stripe

Do I set up webhooks in Stripe?

No. Publishing a workflow with a Stripe trigger makes its webhook endpoint in your Stripe account, and every publish makes it again. Deleting the workflow, or changing it to start another way, removes the endpoint.

Can I build with test keys and go live later?

Yes. A test key only ever moves test money. Most people keep a test connection for building and a live one for the published workflow, and switch the steps over before publishing.

Can a refund be sent twice by mistake?

A retry of the same step sends the same idempotency key, so Stripe refunds once. Run again, Test run and Run this step start a new run with a new key, which is why a test run with a live key asks first.

Which permissions does a restricted key need?

Balance read for the connection test, then write for what your steps use — Customers, Invoices, Refunds, Subscriptions, or Payment Links or Checkout Sessions with Prices and Products. Triggers need Webhook Endpoints write.