ActionTextLinkUpdated September 2026
How do I send an SMS with TextLink?
Short answer: You can send sms in TextLink by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the TextLink Send SMS action to a workflow, map its 2 inputs 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 |
|---|---|---|---|
Phone Number phone_number | string | Required | Recipient phone number in E.164 format |
Message text | string | Required | SMS message text |
Sample request
{"phone_number": "+1234567890","text": "{{trigger.text}}"}
Returns
{"ok": true,"cost": 0.01,"status": "sent","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 Send SMS.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send SMS.
What does the Send SMS action do in TextLink?
Sends an SMS via TextLink to the supplied phone number. TextLink targets developer-friendly transactional and 2FA messaging in the US.
What inputs does Send SMS require?
Required: Phone Number, Message. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Send SMS support batch operations?
Run Send SMS 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