ActionTextLinkUpdated September 2026
How do I list SMS messages sent via TextLink?
Short answer: You can list sent messages in TextLink by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the TextLink List Sent Messages 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.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Page page | string | Optional | Page number for pagination |
Sample request
{"page": "1"}
Returns
{"ok": true,"data": [{"cost": 0.01,"text": "Hello, this is a test message","status": "delivered","sent_at": "2025-03-15T10:00:00Z","message_id": "msg_abc123","phone_number": "+1234567890"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Sent Messages.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Sent Messages.
What does the List Sent Messages action do in TextLink?
Lists SMS messages previously sent through TextLink with their status and timestamps. Use it for audit, reconciliation, or building a sends report.
What inputs does List Sent Messages require?
List Sent Messages has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if TextLink returns an error?
The run history shows the failed step with its input and the error message TextLink returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Sent Messages support batch operations?
Run List Sent Messages inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within TextLink's rate limits.
More actions