A Stripe connection uses a secret key from your own Stripe account. Stripe steps work in that account, and Stripe charges its own fees on each payment.

Who can do this

Workspace Admins and Editors, on any plan — Stripe is not a premium connection. Viewers see the connection but cannot add or change it.

On Stripe's side, someone who can see or create API keys in the Stripe Dashboard — usually an Administrator or Developer.

Before you start

A Stripe account. Test keys work straight away; live keys need the account to be activated in Stripe.

Steps

In Stripe, find the key:

  1. Sign in to the Stripe Dashboard.
  2. Choose test mode (or a sandbox) for a test key, or live mode for a live one. Each has its own keys.
  3. Go to Developers, then API keys.
  4. Copy the Secret key — it starts sk_test_ or sk_live_. Stripe may show a live secret key only once, when it is made.

Or make a restricted key, which can do only what you allow:

  1. On the same page, select Create restricted key.
  2. Name it — Bizomate.
  3. Give it the permissions the steps you use need — see Permissions for a restricted key below.
  4. Select Create key, and copy it. It starts rk_test_ or rk_live_.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Payments, select Stripe. It reads "Stored credential".
  3. In Connection name, type a name — for example Consulace Stripe test.
  4. Paste the key in Secret key — Stripe Dashboard › Developers › API keys. A restricted key (rk_…) works too — give it what its steps use. A test key (sk_test_) never moves real money. It is hidden as you type.
  5. Leave Test the connection before saving ticked. Bizomate asks Stripe for the account's balance before keeping the key.
  6. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace Stripe test” is ready. Every workflow in this workspace can use it."

What happens next

  • A test key shows the Test mode pill on Connections, on every step that uses it, and in the step's settings.
  • Stripe steps list it under Connection: Create a customer, Find a customer, Create a payment link, Create an invoice, Create a refund, Retrieve a charge or payment, Create a checkout session and Cancel a subscription. Its triggers use it too.
  • Test in the connection's panel answers "Reached Stripe · test mode" or "Reached Stripe · live".

Permissions for a restricted key

To use The key needs
The connection test Balance — Read
Create a customer, Find a customer Customers — Write
Create a payment link Payment Links, Prices and Products — Write
Create a checkout session Checkout Sessions, Prices and Products — Write
Create an invoice Invoices — Write
Create a refund Refunds — Write
Retrieve a charge or payment Charges and PaymentIntents — Read
Cancel a subscription Subscriptions — Write
Any Stripe trigger Webhook Endpoints — Write

A key without what a step needs works for the other steps; that step fails with Stripe's reason.

Good to know

  • Test or live comes from the key. sk_test_ and rk_test_ keys only ever move test money. Keep a test connection for building and a live one for the published workflow — see Steps that move money.
  • Rolling a key in Stripe stops the old one. In Bizomate, open the connection's panel, select Revoke and Revoke connection, then Reconnect, paste the new key and select Reconnect.
  • Triggers make webhook endpoints in your Stripe account when you publish — see Start a workflow from Stripe payment events.

If something goes wrong

What you see Why What to do
"Fill in Secret key." The box is empty. Copy the key from Developers › API keys.
Stripe refused it — "Stripe refused: Invalid API Key provided: … Check the connection's details on Connections. Nothing was saved." The key is wrong, rolled, or cut short. A publishable key (pk_…) is not a secret key. Copy the secret key again.
Stripe refused it — "Stripe refused: … Check the connection's details on Connections. A restricted key needs at least Balance read; give it the permissions its steps use. Nothing was saved." A restricted key without Balance read. Edit the key in Stripe to add it, then try again.
Stripe refused: … in a run, naming a permission The restricted key lacks what that step needs. Add the permission from the table above.
"Could not reach Stripe: …" or "Stripe did not answer within 30 seconds." Stripe could not be reached. Try again in a few minutes.