2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill stripe-integration- _meta.json281 B
- SKILL.md5.7 KB
Overview
This skill provides a Stripe integration that lets you manage Customers, Products, Payouts, Transfers, and other Stripe objects through the Membrane CLI. It exposes common actions for listing and retrieving products, prices, invoices, subscriptions, events, and balances, plus create/update/delete operations for products and prices. Use it to interact with Stripe data without handling raw API auth or token refresh yourself.
How this skill works
The skill uses Membrane as a connector and proxy layer: Membrane handles authentication, credential refresh, pagination, and error handling. You install and authenticate the Membrane CLI, create a Stripe connection, then run pre-built Membrane actions or proxy direct Stripe requests through the connection. Actions accept JSON input and return structured output, while the proxy forwards custom API calls with automatic auth headers.
When to use it
- You need to list or inspect Stripe products, prices, customers, invoices, subscriptions, or events.
- You want to create, update, or delete products and prices without storing Stripe API keys locally.
- You need to retrieve account balance, charges, refunds, or payment intents.
- You must run custom Stripe API endpoints not covered by pre-built actions.
- You want credential management (refresh) and pagination handled automatically.
Best practices
- Always use Membrane pre-built actions when possible — they save tokens and handle pagination and edge cases.
- Create a connection through Membrane rather than sharing API keys; Membrane manages the full auth lifecycle.
- Run action discovery (membrane action list --intent=QUERY) before building custom calls to find existing actions.
- Use the Membrane proxy for requests not available as actions and include --json or --rawData when passing bodies.
- Log and inspect action inputSchema from Membrane to pass correct parameters and avoid errors.
Example use cases
- List products and prices for a storefront and sync them to your catalog service.
- Retrieve a customer and their subscriptions to display billing status in an admin dashboard.
- Create a new product and price for a promotional offer via a single Membrane action.
- Fetch recent Stripe events to reconcile webhooks and audit account activity.
- Proxy a custom Stripe endpoint (e.g., reporting or tax features) when no action exists.
FAQ
No. Membrane handles credentials and token refresh; create a connection instead of storing API keys.
Can I call endpoints not exposed as actions?
Yes. Use membrane request CONNECTION_ID /path/to/endpoint to proxy custom Stripe API calls with automatic auth.
How do I discover available actions?
Run membrane action list --intent=QUERY --connectionId=CONNECTION_ID to see action ids and inputSchema for each capability.