Short answer: You can get paddle customer in Paddle by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Paddle Get Paddle Customer action to a workflow, map its 1 input 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 |
|---|---|---|---|
Customer ID customer_id | string | Required | – |
{"customer_id": "{{trigger.customer_id}}"}
{"data": {"id": "ctm_abc","name": "Jane Doe","email": "jane@x.com","status": "active","marketing_consent": true}}
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.