Automate Linear + Stripe
Fast issue tracking that deserves fast automation. Payments, subscriptions and the events behind revenue. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Meeting Follow-Through is a ready-made agent built around Linear; point its last step at Stripe to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Stripe is a decision about the Linear event rather than a transcription of it.
When an issue is created in Linear…
…an agent can look up customers and charges in Stripe — after reading the context and deciding it should.
When a status changes in Linear…
…an agent can summarise revenue activity in Stripe — after reading the context and deciding it should.
When a cycle ends in Linear…
…an agent can flag anomalies in Stripe — after reading the context and deciding it should.
When a payment succeeds or fails in Stripe…
…an agent can create issues with full context in Linear — with the reasoning recorded in the run’s receipt.
When a subscription changes in Stripe…
…an agent can update status and assignees in Linear — with the reasoning recorded in the run’s receipt.
When a dispute opens in Stripe…
…an agent can write cycle summaries in Linear — with the reasoning recorded in the run’s receipt.
Copy this Linear → Stripe workflow
Start with a custom-api call to api.linear.app and the stripe-invoice node. Configure the Linear source payload, the agent input, and the Stripe operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "be9dd0e4-f501-4e38-aad3-b06c73a70e1c",
"name": "Linear → Stripe",
"nodes": [
{
"id": "7b7d6e05-33f6-4f83-a474-4dca5e97502e",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "0bd4ddb1-84de-445d-aa39-d6f08559cbf2",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Linear item. Decide whether it warrants action in Stripe, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "51a04631-9167-45cf-a0ab-897816a0f046",
"text": "Configure destination in Stripe",
"x": 512,
"y": 528,
"isEditing": false,
"type": "stripe-invoice",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"customerEmail": "CONFIGURE_CUSTOMEREMAIL",
"dueDate": "CONFIGURE_DUEDATE",
"currency": "USD",
"amount": 1,
"description": "CONFIGURE_DESCRIPTION",
"lineItems": []
},
"description": "Setup template for Stripe API. Create and send a Stripe invoice with support for single or multiple line items Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "8309eab7-fafa-4776-afbb-f463ace667a4",
"start": {
"id": "7b7d6e05-33f6-4f83-a474-4dca5e97502e",
"type": "output"
},
"end": {
"id": "0bd4ddb1-84de-445d-aa39-d6f08559cbf2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "fea03574-9416-47bf-af0d-5a15ff716a7a",
"start": {
"id": "0bd4ddb1-84de-445d-aa39-d6f08559cbf2",
"type": "output"
},
"end": {
"id": "51a04631-9167-45cf-a0ab-897816a0f046",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Stripe API
Create and send a Stripe invoice with support for single or multiple line items
- customerEmail — Email address of the customer to bill Current example:
CONFIGURE_CUSTOMEREMAIL. - dueDate — Due date for the invoice (YYYY-MM-DD) Current example:
CONFIGURE_DUEDATE. - currency — Currency for the invoice Current example:
USD. - amount — Amount in cents for single item (e.g., 1000 for $10.00) Current example:
1. - description — Description for single item invoice Current example:
CONFIGURE_DESCRIPTION. - lineItems — Array of line items for the invoice. Each item must have 'description' and 'amount' (in cents). Example: [{"description": "Consulting", "amount": 5000, "quantity": 2}] Current example:
[].
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Linear. Install it, point its last step at Stripe, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect Linear with an API key pasted into the vault and Stripe with an API key pasted into the vault; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and stripe-invoice onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Linear and what was written to Stripe.
Linear and Stripe — common questions
Can I connect Linear to Stripe without writing code?
You can build it entirely from the canvas. Authorise Linear with an API key pasted into the vault, Stripe with an API key pasted into the vault, then tell the agent what support escalations become tracked issues should look like once Stripe is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Linear to Stripe automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Linear item in full and decides — whether it matters, how to summarise it, and what belongs in Stripe. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Linear and Stripe data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Linear or Stripe tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Linear and Stripe run leave behind?
You get an auditable trail rather than a success flag. It shows the Linear context the agent worked from, the judgment it made about failed payments chased automatically, and the exact change applied in Stripe, with approvals attached where you required them.
