Short answer: Drop the "TextLink → Send SMS" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"phone_number": "+1234567890","text": "{{trigger.text}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.