Stripe documentation

Stripe is a developer-first payments platform. Use this connector to read customers, charges and subscriptions, and to trigger flows on payment events.

Payments api_key Updated June 16, 2026

Overview

Stripe

Sync customers, subscriptions, and payments with Stripe.

Flows360 gives operators an end-to-end view of Stripe alongside the rest of their stack — sync the objects that matter, run the actions you need, and trigger workflows on real-time events without writing glue code.

Capability summary

Auth methodapi_key
Required scopes6
Objects / actions5 / 3

Authentication

Auth method: api_key

Required scopes

customers:read invoices:read invoices:write charges:read subscriptions:read events:read

Supported objects

Object Read Write Notes
Customer Yes No Represents a customer of your business. It is required for creating subscriptions and invoices.
Invoice Yes Yes Represents a bill for a subscription or a one-off charge. Can be created and read via the API.
Charge Yes No Represents a single attempt to collect payment from a customer's card or other payment method.
Subscription Yes No Represents a customer's recurring subscription to a product or service.
Payment Intent Yes No Represents an intent to collect payment from a customer, tracking the lifecycle of the payment from creation to success or failure.

Supported actions

Action Description
Create Invoice Creates a new draft invoice for a specified customer. The invoice can then be finalized and sent.
List Payments Retrieves a list of charges (payments). The list can be filtered by customer, creation date, and other criteria.
Payment Received Trigger Triggers a flow when a `charge.succeeded` event is received from Stripe, indicating a successful payment. Requires webhook configuration.

Setup steps

  1. Log in to your Stripe Dashboard.
  2. Navigate to the Developers section in the left-hand menu, then click on API keys.
  3. Your API keys are shown on this page. For security, we recommend creating a new Restricted key for use with Flows360 rather than using a secret key.
  4. Click + Create restricted key. Give the key a descriptive name, like "Flows360 Connector".
  5. Grant the key the required permissions for the objects and actions you intend to use. At a minimum, this will include Read permissions for Customers, Invoices, Charges, and Subscriptions, and Write permissions for Invoices if you plan to use the create_invoice action.
  6. Click Create key at the bottom of the page.
  7. A modal will appear showing the restricted key. Copy this key (it will start with rk_live_) and paste it into the API key field in Flows360. This key will only be shown once.

Limitations

  • This connector is subject to Stripe's API rate limits. Please refer to the official Stripe API documentation for the most up-to-date information on rate limiting rules.
  • When using restricted API keys, ensure the key has been granted the necessary permissions for the specific objects and actions you are attempting to access.
  • The payment_received event trigger relies on Stripe webhooks. You must configure a webhook endpoint in your Stripe settings pointing to Flows360.

Use cases & industries

Use cases

CRM to ERP SyncCustomer 360Finance & BillingRevenue Operations

Industries

E-commerce & RetailFinancial ServicesProfessional ServicesSaaS

Start your structured rollout today.

Don’t leave your orchestration to chance. Implement the governance engine used by disciplined operational teams worldwide.

Deploy Flows360 Book a Demo →