Short answer: You can create charge in Stripe by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Stripe Create Charge action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Amount (cents) amount | string | Required | Amount (cents). e.g. "1000" |
Currency currency | options | Required | Currency. Options: USD, EUR, GBP |
Source/Token source | string | Required | Source/Token. e.g. "tok_visa" |
Description description | string | Optional | Description |
Customer ID customer | string | Optional | Stripe customer ID — starts with 'cus_'. Find via List Customers. |
{"amount": "1000","currency": "{{trigger.currency}}","source": "tok_visa","description": "{{trigger.description}}","customer": "e.g. cus_NffrFeUfNV2Hib"}
{"id": "ch_abc","amount": 1000,"status": "succeeded","currency": "usd"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.