Menu

Mattering Automations Stripe integration

Connect Stripe to Mattering Automations: customers, invoices, subscriptions, and balance as workflow steps, plus webhook triggers for paid invoices, succeeded payments, and subscription changes.

The Mattering Automations Stripe integration adds Stripe to your automation canvas: create customers and invoices, read a customer, their subscriptions, or your balance, and start workflows the moment an invoice is paid, a payment succeeds, or a subscription changes.

Setup takes a few minutes: copy a secret key from the Stripe Dashboard, attach it as a credential in Mattering, and register a webhook endpoint if you want the trigger nodes. This guide walks through each step and ends with the full node reference.

One node in this integration moves money. Create Stripe Charge posts a real charge against a real customer when the attached key is a live mode key. Build and verify everything with a test mode key first, and keep that node behind a condition or an approval step rather than wiring it straight to a trigger.

Before you start

  • A Stripe account with permission to view API keys in the Dashboard.
  • A Mattering workspace with access to the Automations app.
  • A test mode secret key, the one that starts with sk_test_, for building and verifying. Attach a live key only after the workflow behaves the way you expect.
  • For trigger nodes: permission to add a webhook endpoint in the Stripe Dashboard.

Create a Stripe secret key

Mattering authenticates to Stripe with a secret API key, sent as a bearer token on every request. Stripe keeps two separate sets of keys and two separate sets of data: test mode and live mode. Which key you attach decides which one your automations touch.

In the Stripe Dashboard, open Developers > API keys.
Confirm which mode you are in using the Test mode toggle. A test key starts with sk_test_ and a live key starts with sk_live_.
Copy the Secret key for that mode. Stripe reveals it on click and, for newly created keys, shows the value once.
Start with the test mode key. A live mode key means the action nodes operate on real customers, real invoices, and real charges from the first test run.
Restricted keys work too if you prefer narrower access, but grant them write permission on the resources your automations create, or those nodes will fail while read-only nodes keep working.

Connect Stripe to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Stripe from the list.
Click Create new credential, paste your secret key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls Stripe's balance endpoint and reports whether the key it accepted is a test mode or a live mode key. Read that result, it is your confirmation of which data set you just connected.
Click Connect. All 9 Stripe nodes appear in your canvas palette.

How webhook triggers deliver

Stripe pushes events to Mattering the moment they happen; no polling, no schedules.

Event happens

A payment succeeds, an invoice is paid, or a subscription changes

Delivery to your webhook URL

Mattering reads the event type and matches it to your trigger nodes

Your workflows run

Every active automation containing the trigger node fires

Verify it works

After connecting, open any automation canvas and check the palette: a Stripe section should list the query, action, and trigger nodes. Verify with a read-only node. Drop Stripe Balance onto the canvas and run a test step; a successful response returns your balance object. Do not verify the integration with Create Stripe Charge, and keep a test mode key attached while you are still testing anything.

For triggers, open the trigger node's config panel: it shows the webhook URL minted for your Stripe connection, with a copy button. In the Stripe Dashboard, open Developers > Webhooks > Add endpoint, paste that URL, and subscribe to the events you want: payment_intent.succeeded for Stripe Payment, invoice.paid for Stripe Invoice Paid, and customer.subscription.created, customer.subscription.updated, and customer.subscription.deleted for Stripe Subscription Updated.

Set the automation containing the trigger to active, then use Stripe's own Send test webhook control on the endpoint to send one of those events. Stripe's endpoint page shows the response it got back from Mattering, and every active automation in your organization containing that trigger node runs with the event payload.

Node reference

9 nodes, generated from the connector itself so this reference always matches what ships.

Trigger nodes (start workflows from events) 3

Stripe Invoice Paid

trigger_stripe_invoice_paid

Fires when an invoice is paid

Stripe Payment

trigger_stripe_payment_succeeded

Fires when a payment succeeds

Stripe Subscription Updated

trigger_stripe_subscription_updated

Fires when a subscription changes

Read and query nodes 3

Stripe Balance

query_stripe_balance

Get current Stripe balance

Stripe Customer

query_stripe_customer

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

Stripe Subscriptions

query_stripe_subscriptions

List subscriptions for a customer

Action nodes 3

Create Stripe Charge

action_stripe_create_charge

Create a one-time charge

Create Stripe Customer

action_stripe_create_customer

Create a new Stripe customer

Create Stripe Invoice

action_stripe_create_invoice

Create and optionally send a Stripe invoice

Using the integration

On the automation canvas

Stripe nodes chain with every other node: a paid invoice can close a task in Mattering Productivity, a subscription change can update a record in a Mattering database, and Stripe Customer can hydrate the rest of a workflow from the customer id an event carries.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can look up a customer, list their subscriptions, and read your balance through the same nodes your workflows use. Those three queries are read-only, which makes them the safest Stripe surface to hand an agent.

Webhook triggers

Succeeded payments, paid invoices, and subscription changes start workflows without polling. Place the trigger node in an automation, set the automation to active, and register the webhook URL once per Stripe account. Every trigger payload carries a livemode field, so a workflow can branch on whether the event came from test or live data.

Before you use the charge node

Create Stripe Charge creates a charge against the customer you name, using the payment method Stripe holds for them. It takes an amount, a currency that defaults to usd, a customer, and a description, and the amount is in the currency's smallest unit, so 2500 is 25.00 USD. Put a condition, an approval step, or a manual run in front of it, and prove the whole path on a test mode key before a live key goes anywhere near it.

Troubleshooting

Test Connection fails with a 401
The key is wrong, was rolled, or picked up stray whitespace when pasted. Copy it again from Developers > API keys in the Dashboard and update the credential on the connector. Stripe rejects a key from a deleted or rolled pair immediately.
Test Connection passes but action nodes fail with a permission error
This is the signature of a restricted key. The connection test only reads your balance, so a key with read access passes it while a node that creates a customer, invoice, or charge is refused. Grant the restricted key write permission on those resources in Stripe, or attach a standard secret key.
Lookups return nothing, or Stripe says the customer does not exist
Test mode and live mode are separate data sets. A cus_ id, invoice, or subscription created in live mode does not exist in test mode, and the reverse is also true. Check which key is attached, the Test Connection result tells you, and use ids from the same mode.
Stripe Customer returns a not found error for a valid customer
Stripe Customer fetches by Stripe customer id, the value starting with cus_, not by email address. If the workflow only has an email, take the customer id from the trigger payload of a Stripe event instead, which carries it on payment, invoice, and subscription events.
The trigger never fires
Check four things: the automation containing the trigger node is set to active, the webhook endpoint is registered in Stripe with the Mattering URL from the trigger node's config panel, the endpoint is subscribed to the specific event, and Stripe's endpoint page shows a 200 response from Mattering on recent deliveries. Note which events map: Stripe Payment listens for payment_intent.succeeded, so a charge created through the Charges endpoint, including one from Create Stripe Charge, does not fire it.
Stripe reports 401 Invalid signature on deliveries
Mattering verifies Stripe's signature when a webhook signing secret is stored on the connector's configuration. A 401 means the stored secret does not match the signing secret Stripe shows for that endpoint, or the delivery timestamp fell outside Stripe's tolerance window. Copy the signing secret from the endpoint in Stripe again and store the current value. With no signing secret stored, deliveries are accepted unverified, so treat the webhook URL as a secret.
A created invoice has no line items on it
Create Stripe Invoice creates the invoice for a customer and can set the auto_advance flag that controls whether Stripe collects on it automatically. It does not create line items, so the items have to exist in Stripe for that customer already. Add them through Stripe or with the generic HTTP Request node against Stripe's invoice items endpoint using the same credential.

Stripe is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products