Skip to main content
cronable
Stripe integration

Stripe automation, on a machine you control.

Payments are the events a business cares about most. Cronable reacts to them the moment Stripe sends them, registering the webhook for you, and reads your balance, charges, customers and invoices for reports. The built-in reads never move money.

StripeStripe · ActionStripe webhook · Trigger
All integrations
One workflow, end to end

A Stripe workflow on the canvas

Each card is one job. A wire means the next job runs when the one before it succeeds, or when it fails.

jobs/finance
Or type it to the assistant

“When a Stripe payment fails, tell #finance in Slack with the customer’s email and the amount.”

What you can do

Every Stripe step Cronable ships

Actions

Steps a workflow can take in Stripe.
  • Check the balance

    Read your available and pending balance, for a daily cash check.

  • List charges

    Return recent charges, optionally for one customer, with paging.

  • List customers

    Return your customers, or only those with an exact email address.

  • List invoices

    Return invoices filtered by customer or by status: draft, open, paid, uncollectible or void.

  • Custom request

    Call any other Stripe endpoint. This is where writes live, so pair it with a restricted or test-mode key.

Triggers

What starts a Stripe workflow.
  • Stripe events

    Pick a Stripe credential and Cronable registers the webhook endpoint for you. It listens for successful and failed payments, paid and failed invoices, subscriptions created, updated or cancelled, and completed checkouts. Signatures are verified out of the box.

Popular workflows

Stripe workflows worth automating first

01

Failed-payment alerts

The Stripe trigger fires on a failed payment, a Filter step keeps the ones that matter, and Slack tells finance who to contact.

02

The morning cash number

At 8am a job reads your Stripe balance and posts available and pending funds to Slack, or appends them to a Google Sheet for a running history.

03

Subscription changes in the CRM

When a subscription is created or cancelled, update the matching contact in HubSpot so sales sees churn the same day.

04

Month-end invoice report

On the first of the month, list open invoices, let an AI step group them by customer, and email the summary to your bookkeeper.

How you connect

Connecting Stripe

Stripe connects with a key you paste. No OAuth flow, no Stripe app.

  1. 1For read jobs, store a Stripe secret key, or better a read-only restricted key (rk_…), as a bearer token credential.
  2. 2For the trigger, pick a credential holding your secret key: Cronable creates the webhook endpoint and stores its signing secret. Delete the job and the endpoint is removed.
  3. 3Events reach your machine through Cronable’s hosted relay, so no port is opened. Inbound webhooks are included from the Basic plan.
Why Cronable

Your Stripe automation, on your own machine

Runs on your own machine

Install Cronable as a Mac or Windows app, or on a server you own. Your Stripe jobs, secrets and run history stay on that machine by default.

Built from one sentence

Describe the workflow in plain English and the built-in assistant builds the jobs, the schedule and the failure handling for you to review on the canvas. On every plan, including Free.

Unlimited runs

Plans count the jobs you define, not how often they fire. A job that touches Stripe every hour costs the same as one that runs once a month.

Credentials encrypted locally

Keys and tokens are AES-256-GCM encrypted in a local database, referenced from jobs by name and masked out of logs and run output.

Questions

Stripe automation, answered

Can Cronable start workflows from Stripe events?

Yes. The Stripe trigger registers its own webhook endpoint and starts a run for each payment, invoice, subscription or checkout event, with the full event available to the next step.

Is it safe to give Cronable a Stripe key?

The built-in operations only read, so a reporting job cannot move money; use a restricted read-only key for those. Any key is encrypted on your machine, sent only in the Authorization header and masked in logs.

Do I set up the webhook in the Stripe Dashboard?

No. Choose a credential and Cronable creates the endpoint, stores the signing secret and verifies every event. You can still wire one up by hand and paste its whsec_ secret if you prefer.

Can Cronable create charges or refunds?

Not with a built-in operation. Writes go through a custom request, which you set up explicitly, ideally with a restricted or test-mode key.

Does my machine need to be reachable for webhooks?

No port has to be opened. Stripe posts to Cronable’s hosted relay, which forwards the event to your install over a connection your machine opens outward. Webhooks are on paid plans, from Basic up.

Anything you do twice in Stripe is cronable.

Refund checks, dunning, the morning cash number: all of it is cronable.