Payments · 43 pre-built actions
Stripe integration with Nexus
Turn Stripe billing events into governed finance steps. Stripe events start runs directly, and product, core resource and billing actions let payments and subscriptions reach accounting, CRM and ERP.
Pre-built actions
What you can automate
43 pre-built Stripe actions, grouped by what they work on.
43
PRE-BUILT ACTIONS
- 01Billing actions work with invoices and subscriptions.
- 02Core Resources actions work with customers, payments and related objects.
- 03Products actions keep the product catalog aligned.
Workflow
How it fits into a Nexus workflow
Stripe is a trigger source in Nexus. An event can start a governed run directly, and Stripe steps then run as pre-built actions in the same workflow.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Stripe API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Payment to accounting
A Stripe payment is matched and recorded in Xero or your ERP.
Subscription change to CRM
A subscription change is reflected on the Salesforce account.
Refunds with approval
Refunds above a threshold pause for finance.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Integration patterns
Stripe integration patterns
Dedicated patterns that pair Stripe with another system in one governed run.
Industry use cases
Processes that use Stripe
Financial services
Payment reconciliation and exception handling
Payments reconcile into accounting automatically, and mismatches become tracked exceptions.
Enterprise
Order to cash across CRM, ERP and billing
Won deals become orders and invoices without re-keying, with exceptions reviewed.
Financial services
Subscription revenue reconciliation
Billing events are compared with NetSuite and Xero, and differences are approved before correction.
FAQ
Stripe connector questions
- Which Stripe actions are pre-built?
- Nexus includes 43 pre-built Stripe actions across Products (8), Core Resources (16) and Billing (19).
- Can Stripe start a workflow?
- Yes. Stripe is a trigger source, so an event can start a run directly.
- What if the operation I need is not pre-built?
- Use the Stripe API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Xero connector
Invoices, payments and bank transactions.
- Salesforce connector
Leads, accounts, opportunities and cases.
- SAP connector
Finance, procurement and sales orders.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Stripe fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.