Nodes›App nodes
Stripe
Stripe explains how this part of Flowline works and how to use it in a real workflow. This page is dummy content for testing the Cloudairy wiki: structure, navigation, search and rendering.
Note: Flowline is a fictional automation product. Section: Nodes › App nodes.
Prerequisites
- A Flowline account (cloud or self-hosted)
- Editor access to the project
- About 24 minutes
How it works
Every workflow starts with a trigger, passes items from node to node, and ends when the last node finishes. Stripe fits in the middle of that chain: it receives items, does its work, and hands the result to the next node. Use $json to read the current item and $node["Name"] to reach an earlier node.
Step-by-step
- Open the workflow editor and select Add node.
- Search for Stripe and add it to the canvas.
- Fill in the required parameters (see the table below).
- Select Test step to run it with sample data.
- Check the output panel, then Save the workflow.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| Name | string | Yes | A label shown on the canvas |
| Mode | option | Yes | run once or run per item |
| Timeout | number | No | Seconds before the step fails (default 109) |
| Retry on fail | boolean | No | Retries up to 3 times with back-off |
Example
# Stripe
services:
flowline:
image: flowline/flowline:latest
ports: ["5678:5678"]
environment:
- DB_TYPE=postgres
- QUEUE_MODE=redis
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Step shows No output | The previous node returned zero items | Pin sample data on the previous node |
401 Unauthorized |
Expired credential | Reconnect it under Credentials |
| Execution times out | Large payload | Split items with Split Out |
Related
- Build your first workflow
- Expressions
- Error handling
Was this helpful?