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.
Workflows fire when something happens in Linear.
- Comment CreatedWebhook
- New CycleWebhook
- New IssueWebhook
- Issue DeletedWebhook
- Issue UpdatedWebhook
Workflows do something in Stripe, instantly.
- Cancel SubscriptionAPI
- Create ChargeAPI
- Create Checkout SessionAPI
- Create CouponAPI
- Create CustomerAPI
- Create Payment IntentAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Linear, do it in Stripe.
6 Linear triggers wired to 31 Stripe actions. Most-used pairing: Comment Created → Cancel Subscription.
Or fire it the other way around.
10 Stripe triggers wired to 8 Linear actions downstream.
See Stripe → Linear →Common Linear → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.
Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.
Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.
Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.
Connect Linear and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Linear and Stripe
Open Tiny Command, authorize Linear and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Linear trigger
Drop the Linear → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/linear.trigger-comment-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the Linear payload into the Stripe inputs.
stripe.cancel-subscription - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Linear + Stripe.
How do I pay a contractor on Linear issue close?
Can I update Stripe pricing on a Linear release?
How do I avoid double-paying contractors on Linear issue re-closes?
Can I create Linear issues from Stripe error events?
How do I track Linear-driven revenue events?
When does Linear + Stripe make sense?
Other apps that pair well with Linear.
Wire Linear to Stripe in 2 minutes.
Free tier available. No credit card. No onboarding call.
