AI agents for Stripe
Payments, subscriptions and the events behind revenue. AGNT connects to Stripe so agents can read what happens there, reason about it, and act — with a receipt for every run.
Report Assembler is a ready-made agent that works in Stripe — free, and it runs on your machine.
Stripe and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Stripe. |
|---|---|
| Connects with | An API key held in the local vault |
| AGNT node | stripe-invoice |
| Runs when | A payment succeeds or fails |
| Typical build time | Two minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- a payment succeeds or fails
- a subscription changes
- a dispute opens
Agents can…
- look up customers and charges
- summarise revenue activity
- flag anomalies
Teams use it for
- failed payments chased automatically
- revenue digests every Monday
- churn signals routed to the right person
The Stripe workflow, to configure
Design goal for Stripe: failed payments chased automatically; revenue digests every Monday; churn signals routed to the right person. The template below supplies configurable nodes, not the complete logic for those goals.
Use this Stripe setup template to arrange the schedule, input review and API operation. Configure the account-specific fields and add your own decision and approval controls before activation.
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": "f3277be4-31bd-4361-a4b4-e81f4860defa",
"name": "Stripe — read, decide, act",
"nodes": [
{
"id": "473ad2ef-27f9-4622-ab88-0c1bbb09e4d4",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "clock",
"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": "be1c642d-d4c2-4ff9-a1d1-4d0c5545ae1e",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Stripe item and decide whether it warrants action. Explain your reasoning.\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": "12e02d82-9850-4260-a4da-55faca46d4d8",
"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": "671ca5d0-11ce-4297-ac75-c0955ce55732",
"start": {
"id": "473ad2ef-27f9-4622-ab88-0c1bbb09e4d4",
"type": "output"
},
"end": {
"id": "be1c642d-d4c2-4ff9-a1d1-4d0c5545ae1e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "fe8d2eed-7d8a-4a55-a10c-a9487eabaff6",
"start": {
"id": "be1c642d-d4c2-4ff9-a1d1-4d0c5545ae1e",
"type": "output"
},
"end": {
"id": "12e02d82-9850-4260-a4da-55faca46d4d8",
"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 Report Assembler — it runs on Stripe
Report Assembler is a working agent that uses Stripe. Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
Revenue events worth reacting to
Stripe emits exactly the events a business should respond to promptly: a failed payment, a subscription change, a dispute opening. Reacting the same day rather than at month end is usually the whole value, and it requires only that something is watching.
Numbers with a narrative
Revenue reporting is more useful when somebody explains the movement. An agent with access to both the payment data and the surrounding context can attempt that explanation rather than presenting a figure and leaving it there.
Stripe node reference
Create and send a Stripe invoice with support for single or multiple line items
Full Stripe API parameter reference
| Parameter | Type | What it does |
|---|---|---|
customerEmailrequired |
string | Email address of the customer to bill |
dueDaterequired |
string | Due date for the invoice (YYYY-MM-DD) |
currencyrequired |
string | Currency for the invoice USD · EUR · GBP · JPY |
amountrequired |
number | Amount in cents for single item (e.g., 1000 for $10.00) |
descriptionrequired |
string | Description for single item invoice |
lineItemsrequired |
array | Array of line items for the invoice. Each item must have 'description' and 'amount' (in cents). Example: [{"description": "Consulting", "amount": 5000, "quantity": 2}] |
Every parameter above is read from the shipped stripe-invoice node, so it cannot drift from the product.
Connect Stripe in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect by pasting an API key into AGNT’s vault — stored encrypted on your machine, never uploaded.
- Drop the Stripe node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Stripe + AGNT — common questions
Can failed payments be chased automatically?
Yes — a failure can trigger a workflow that drafts outreach and flags the account.
Can it produce revenue digests?
Yes, on a schedule, with the figures traceable to the underlying charges.
How is Stripe connected?
With an API key stored encrypted in the local vault; a read-only key is sufficient for reporting.