Skip to content

Starter

Create an issue in Linear when a payment fails in Stripe

When a payment fails in Stripe, create an issue in Linear.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Steps
1
Client fills in
1
Accounts
2
Starts
A payment fails in Stripe, within seconds

UsesBeta

Every step, in order

When it happens in the first app, the step runs in the second, with the client’s own account.

A payment fails
A Stripe invoice payment attempt declined, or no card on file, within seconds. Once per attempt: Smart Retries can fire it again for the same invoice. The restricted key needs Webhook Endpoints: write.
Create an issue
An issue in a team. The output is the new issue: its identifier and link.
  1. Starts whenA payment fails
  2. App stepCreate an issue

What each client fills in

Linear: Team ID
For example the team’s UUID

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

  • In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.

  • In the client’s Linear: Settings → Security & access → Personal API keys → New API key. The triggers make webhooks, which needs a workspace admin’s key.

After you install it

It lands switched off. The client’s checklist holds exactly this:

  1. Connect the client’s Stripe, for “A payment fails”
  2. Connect the client’s Linear, for “Create an issue”
  3. Fill in Linear: Team ID (For example the team’s UUID)

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.