ActionSms77Updated September 2026
How do I send a voice call via Sms77?
Short answer: You can sms77 send voice in Sms77 by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Sms77 Sms77 Send Voice 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 |
|---|---|---|---|
Message message | textarea | Required | Message. (multi-line text) |
Sample request
{"message": "{{trigger.message}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Sms77 Send Voice.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Sms77 Send Voice.
What does the Sms77 Send Voice action do in Sms77?
Initiates a TTS voice call to a number. Useful for high-priority alerts where SMS might be missed.
What inputs does Sms77 Send Voice require?
Required: 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 Sms77 returns an error?
The run history shows the failed step with its input and the error message Sms77 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 Sms77 Send Voice support batch operations?
Run Sms77 Send Voice 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 Sms77's rate limits.
More actions