ActionSms77Updated May 2026

How do I send SMS via Sms77?

Short answer: Drop the "Sms77 → Sms77 Send SMS" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Sms77 actions

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 SMS.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Sms77

2 Google Sheets triggers

HubSpot → Sms77

18 HubSpot triggers

FAQ

Questions about Sms77 Send SMS.

What does the Sms77 Send SMS action do in Sms77?

Sends SMS via the German-origin gateway. Strong in DACH and European markets at competitive pricing.

What inputs does Sms77 Send SMS 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Sms77 Send SMS support batch operations?

Yes. Run Sms77 Send SMS inside a Loop node to process arrays. Tiny Command handles Sms77's rate limits automatically so you don't have to throttle manually.

More actions