RingCentral Send SMS: RingCentral action

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
From Phone Number from	string	Required	One of your RingCentral SMS-enabled numbers in E.164 format.
To Phone Number to	string	Required	Recipient number in E.164 format.
Message text	string	Required	Hi there!

Sample request

{
  "from": "+15551234567",
  "to": "+15559876543",
  "text": "Hi there!"
}

Returns

{
  "id": "12345",
  "to": [
    {
      "phoneNumber": "+15559876543"
    }
  ],
  "from": {
    "phoneNumber": "+15551234567"
  },
  "subject": "Hi there!",
  "messageStatus": "Queued"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about RingCentral Send SMS.

What does the RingCentral Send SMS action do in RingCentral?

Sends an SMS from a RingCentral number. For business-SMS workflows that need to keep all customer communication in the RingCentral inbox.

What inputs does RingCentral Send SMS require?

Required: From Phone Number, To 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 RingCentral 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 RingCentral Send SMS support batch operations?

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

More actions