Per-pair page

Linear + Stripe: payments tied to engineering milestones.

Trigger Stripe events from Linear issues (contractor payouts, usage-billing tied to features), or create Linear issues from Stripe-found bugs.

Trigger app
Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →
Action app
Linear as the action

Workflows do something in Linear, instantly.

Connect Stripe to Linear — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Stripe → Linear

When something happens in Stripe, do it in Linear.

10 Stripe triggers wired to 8 Linear actions. Most-used pairing: Charge Failed → Add Comment.

Linear → Stripe

Or fire it the other way around.

6 Linear triggers wired to 31 Stripe actions downstream.

See Linear → Stripe →
Popular pairings

Common Stripe → Linear workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 80 combinations
When charge failed in Stripe, add comment in Linear.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, create issue in Linear.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, get issue in Linear.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, list issues in Linear.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When checkout completed in Stripe, add comment in Linear.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, create issue in Linear.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, get issue in Linear.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, list issues in Linear.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When new customer in Stripe, add comment in Linear.

Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.

How it works

Connect Stripe and Linear in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Stripe and Linear

    Open TinyCommand, authorize Stripe and Linear once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Stripe trigger

    Drop the Stripe → Charge Failed trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/stripe.trigger-charge-failed
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Linear action

    Drop the Linear → Add Comment action below it. Map fields from the Stripe payload into the Linear inputs.

    linear.create-comment
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Stripe + Linear.

How do I pay a contractor on Linear issue close?
Linear Issue moved to "Done" with "milestone" label + contractor metadata → Stripe Create Payment or Connect Transfer. Standard for outsourced work pay-on-delivery.
Can I update Stripe pricing on a Linear release?
Yes. Linear Issue Closed with "pricing-change" label → Stripe Update Product or Create Price for new tier. Code + pricing land together for usage-based products.
How do I avoid double-paying contractors on Linear issue re-closes?
Use Stripe idempotency keys derived from Linear identifier. Stripe returns the original payment instead of creating a duplicate on re-fire.
Can I create Linear issues from Stripe error events?
Yes. Stripe Webhook (error, dispute) → Linear Create Issue in a "Stripe Bugs" team. Engineering tracks Stripe-side issues alongside code bugs in one tracker.
How do I track Linear-driven revenue events?
Log every Linear-triggered Stripe event into Sheet/DB. Useful for attribution: which features (in Linear) drove which revenue. Standard for usage-based growth analysis.
When does Linear + Stripe make sense?
Usage-based SaaS where features affect billing, or contractor payouts where milestone Linear issues trigger payment. Niche but high-leverage when applicable.
Related

Other apps that pair well with Stripe.


Connect Stripe to Linear — start free