SMS
Text the report link
Sends a text message, usually a link to the finished result, to a phone number the moment the job reaches this step.
How it works
SMS is your quick-tap notification. When a job finishes its work, this node fires a short text (typically a link the recipient taps to open the report) to a mobile number. It is the step people actually notice, since almost everyone reads a text within minutes.
You pick the number to text and write the message, dropping in job values like a name or a link so each text is personalized. It is meant for short, action-oriented alerts, not long documents, so pair it with something that hosts the full result behind the link.
US texting to your own customers runs through registered business messaging (10DLC), which keeps carriers from blocking you. If you plan to text at volume, that registration is a one-time setup on your account.
Common use cases
Real situations where this node earns its place in a flow.
Text a status update
Send a short SMS when an application moves forward or a document is ready.
Nudge by text
Text a reminder for a missing document or an unpaid invoice.
Reach phone-first people
Deliver the result by text for audiences who do not check email often.
SMS in a workflow
A simple example of where this node sits in a flow.
What you set up
- Enter the destination phone number, or map it from a value the job already captured (like the applicant's mobile).
- Write the message text and insert job variables such as the report link, name, or reference number.
- Confirm your account's business messaging (10DLC) registration is in place before sending to real customers at volume.
Common questions
Can I attach the actual PDF to a text?
No. A text carries a short message and a link. Host the file first (for example with a report step or S3) and text the link so the recipient taps to open it.
Why do I need business messaging registration?
US carriers filter unregistered business texts. Registering your account once (10DLC) tells carriers you are a legitimate sender so your messages reliably arrive.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
toDestination number; falls back to the confirmed relay recipient.
Type: string (phone)fromSender number in E.164.
Type: string (phone)messagingProfileIdTelnyx messaging profile id used for the send.
Type: stringapiKeyTelnyx API key; resolved from the org secret vault by reference.
Type: string (secret)bodyMessage text; falls back to a relay-supplied default then a built-in default.
Type: string
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "sms-out",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "sms-out",
"kind": "output",
"title": "SMS",
"subtitle": "Text the report link",
"config": {
"to": "",
"from": "",
"messagingProfileId": "",
"apiKey": "",
"body": ""
}
}
}