Menu
Mattering Automations connector

A Stripe MCP with real payment triggers, and one node that moves money

Connect one secret key and Stripe customers, invoices, subscriptions, and balance become workflow steps, while paid invoices, succeeded payments, and subscription changes become triggers. The node that creates a charge is real money, so it is built to be gated, not wired straight to a trigger.

9 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Stripe MCP connector does

The Stripe connector for Mattering Automations is a focused set of nine nodes: create a customer, create an invoice, and create a charge; read your balance, a customer record, or a customer's subscriptions; and start workflows from three Stripe events. That is a deliberate slice of Stripe's API rather than the whole of it. For anything outside the nine, the generic HTTP Request node can call any Stripe endpoint using the same stored key.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can look up a customer, check what they are subscribed to, and open a follow-up task without anyone opening the Stripe Dashboard.

Because Mattering is a work platform rather than middleware, a billing event lands somewhere useful by default: a paid invoice can close a task, a subscription change can update a record in a Mattering database, and the whole flow lives on one canvas next to the rest of the work.

One of the nine nodes moves money. Create Stripe Charge posts a real charge against a real customer in whatever mode your key is in, so it deserves different handling from the read nodes: build and verify with a test mode key, and put a condition or an approval step in front of it rather than connecting it directly to a trigger. The queries and the triggers are safe to explore freely; the charge node is the one to slow down on.

One connection, three surfaces

  • Visual automations. Drag Stripe nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Stripe node, ready to drop on the canvas

9 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Trigger nodes (start workflows from events) 3

Stripe Invoice Paid

Fires when an invoice is paid

Stripe Payment

Fires when a payment succeeds

Stripe Subscription Updated

Fires when a subscription changes

Read and query nodes 3

Stripe Balance

Get current Stripe balance

Stripe Customer

Look up a Stripe customer by customer ID (cus_...). Email lookup is not supported by this node.

Stripe Subscriptions

List subscriptions for a customer

Action nodes 3

Create Stripe Charge

Create a one-time charge

Create Stripe Customer

Create a new Stripe customer

Create Stripe Invoice

Create and optionally send a Stripe invoice

Connecting Stripe takes one credential

Stripe keeps API keys in the Dashboard under Developers, then API keys. Every account has two sets: test mode keys, which start with sk_test_, and live mode keys, which start with sk_live_. Use a test mode key while you build and verify, and move to a live key only once the workflow does exactly what you expect.

1

In the Stripe Dashboard, open Developers, then API keys, and copy a secret key. Start with the test mode key.

2

In Mattering Automations, open Connectors, click Add Connector, choose Stripe, and create a credential with that key.

3

Click Test Connection. Mattering calls Stripe's balance endpoint and reports back whether the key it accepted is a test mode or a live mode key, so you can see which one you attached.

4

All 9 Stripe nodes appear in the canvas palette. Trigger nodes show a webhook URL to register in Stripe under Developers, then Webhooks, subscribed to the events you want delivered.

Common uses for the Stripe MCP

Paid invoices that update the record

Stripe Invoice Paid fires the moment Stripe reports an invoice paid. The workflow reads the customer and amount from the event, closes the chase task in Mattering Productivity, and posts the result to the channel that cares.

Subscription changes the team can see

Stripe Subscription Updated fires on subscription created, updated, and deleted events. Route a plan change or a cancellation into a Mattering database, tag the account, and give the people who own the relationship the news before the customer has to repeat it.

Customers created from the work that wins them

When a deal closes or a form comes in, Create Stripe Customer writes the record in Stripe with the email, name, and description already collected, so nobody retypes it into the Dashboard.

Billing lookups from chat

Stripe Customer, Stripe Subscriptions, and Stripe Balance are read-only. An MCP-connected assistant can answer what a customer is subscribed to or what the balance looks like without touching anything, which makes them the safest nodes to hand an agent.

A charge step that waits for a person

Create Stripe Charge is the one node that moves money. Put a condition, an approval step, or a manual run in front of it so a charge only happens when a human or an explicit rule says it should, and keep a test mode key on the connector until that gate is proven.

Invoices drafted without the copy and paste

Create Stripe Invoice creates the invoice for a customer in Stripe and can set the auto_advance flag that controls whether Stripe collects on it automatically. It does not build line items itself, so it fits accounts where the items already exist in Stripe.

Example: A paid invoice updates the account and tells the team

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: Stripe Invoice Paid fires from Stripe's webhook the moment the invoice is marked paid.

2

A condition checks the livemode field on the event, so test mode payments never touch live records.

3

Stripe Customer looks up the customer id carried in the event payload and returns the full customer record.

4

Stripe Subscriptions lists that customer's subscriptions so the workflow knows what they are actually on.

5

Mattering Productivity closes the open payment task and a message goes to the account channel with the amount, the customer, and the plan.

Stripe MCP questions, answered

What Stripe operations are supported?

Nine nodes. Actions: Create Stripe Customer, Create Stripe Invoice, and Create Stripe Charge. Queries: Stripe Balance, Stripe Customer, and Stripe Subscriptions. Triggers: Stripe Payment, Stripe Invoice Paid, and Stripe Subscription Updated. That is a focused set, not an exhaustive wrapper around Stripe's API. Refunds, payouts, products, prices, checkout sessions, and payment links are not nodes; for those, the generic HTTP Request node can call any Stripe endpoint using the same stored key.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Does the Create Stripe Charge node move real money?

Yes. It creates a charge against the customer you name, using the payment method Stripe has on file for them, in whatever mode the attached key is in. A live mode key means a real charge on a real customer. Build and verify with a test mode key, and gate the node behind a condition, an approval step, or a manual run rather than connecting it directly to a trigger.

Which Stripe API does the charge node use?

Create Stripe Charge posts to Stripe's Charges endpoint, not the PaymentIntents endpoint. Charges is Stripe's older payment path and it does not carry the authentication flow PaymentIntents uses for 3D Secure and Strong Customer Authentication, so a card that needs the customer to authenticate can fail instead of stepping up. If your customers are in a market where SCA applies, read Stripe's own guidance on which API fits before pointing this node at a live key. The node takes an amount, a currency that defaults to usd, a customer, and a description; the amount is in the currency's smallest unit, so 2500 is 25.00 USD.

Can Stripe events start a workflow?

Yes, that is what the three trigger nodes do. Mattering maps payment_intent.succeeded to Stripe Payment, invoice.paid to Stripe Invoice Paid, and customer.subscription.created, customer.subscription.updated, and customer.subscription.deleted to Stripe Subscription Updated. Place a trigger node on a canvas, copy the webhook URL it shows, register it in Stripe under Developers, then Webhooks, and subscribe to those events. Every active automation in your organization containing that trigger node then runs when a matching event arrives.

Are the incoming webhooks verified?

Stripe signs every delivery with a Stripe-Signature header. Mattering checks that signature, including Stripe's timestamp tolerance, when a webhook signing secret is stored on the connector's configuration. If no signing secret is stored, deliveries are accepted without a signature check, so treat the webhook URL itself as a secret and add the signing secret when you want the check enforced.

How do I keep test activity out of live records?

Two ways, and they stack. Attach a test mode key to the connector while you build, which keeps every action and query in Stripe's test data. And branch on the livemode field that every trigger payload carries, so a test event that reaches a live workflow can be routed somewhere harmless instead of updating real records.

What does the customer lookup take?

Stripe Customer fetches a customer by their Stripe id, the value that starts with cus_. If your workflow only has an email address, get the id first, for example from the trigger payload of a Stripe event, which carries the customer id on payment, invoice, and subscription events.

9 nodes waiting on the canvas

Put Stripe to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Stripe is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products