Integrations
Stripe
Create payment links, Checkout sessions, customers, invoices, retrieve payment status, and create refunds.
What this guide covers
- A Stripe account authorized through the Yanola connection flow. An API-key connection route also exists where that option is enabled.
- 6 supported workflow actions.
- Authorize only the Stripe account that should receive live or test payment operations. Stripe permissions and account mode govern which resources are accessible.
- Refunds and invoice operations can create irreversible financial effects; validate identifiers and amounts before live activation.
What Stripe connects
A Stripe account authorized through the Yanola connection flow. An API-key connection route also exists where that option is enabled.
Create payment links, Checkout sessions, customers, invoices, retrieve payment status, and create refunds.
Prerequisites and permissions
- A Stripe account that can create the intended payment resources
- Permission to authorize the account
- Product, price, customer, charge, or payment identifiers required by the selected action
Authorize only the Stripe account that should receive live or test payment operations. Stripe permissions and account mode govern which resources are accessible.
Connect and configure
- Open the intended Agent Project → Integrations.
- Find Stripe and select Connect.
- Complete authorization with the correct external identity.
- Confirm the returned connection status is active.
- In the workflow builder, add App Action.
- Select Stripe, choose one supported action, select the connection, and complete the fields Yanola displays.
- Save and test with controlled data before activation.
Supported actions
| Action ID | What it does |
|---|---|
create_checkout_session | Create a Stripe Checkout payment or subscription session. |
create_payment_link | Create a reusable Stripe Payment Link. |
create_customer | Create a Stripe customer from WhatsApp/contact data. |
create_invoice | Create, finalize, and optionally send a Stripe invoice. |
retrieve_payment | Retrieve a Checkout Session or Payment Intent status. |
create_refund | Refund a Stripe charge or payment intent. |
Example workflow
After a customer confirms an order, create a Checkout session and send its returned URL in a WhatsApp reply.
Workflow Trigger → Validate inputs → App Action (Stripe) → Condition → Notify or End FlowReconnection and token expiration
- Open Integrations when a workflow reports a missing, expired, revoked, or error connection.
- Select Reconnect for Stripe.
- Authorize the intended identity again.
- Validate access to the exact resource used by the workflow.
- Retest every dependent App Action.
Troubleshooting
| Symptom | What to check |
|---|---|
Connection is expired, revoked, or error | Reconnect from Integrations and complete provider consent. |
Action cannot find a resource | Grant the connected identity access and use the exact provider ID. |
Action input is rejected | Match the action-specific fields and data types shown in the node. |
Test and live behavior differ | Check provider environment, current permissions, external rate limits, and live data. |
Limitations and security
Refunds and invoice operations can create irreversible financial effects; validate identifiers and amounts before live activation.
Yanola does not replace Stripe's product catalog, tax, fraud, settlement, or dispute tools.
Never place provider access tokens or secrets in workflow text, logs, screenshots, or AI prompts. Remove unused connections and reconnect only through Yanola.