Sinch Engage icon

Sinch Engage

Send SMS and manage communications via Sinch Engage
Join our community

Actions2

  • Blacklist Actions
  • SMS Actions

Overview

This node sends SMS messages using the Sinch Engage platform. It is useful for automating SMS communications such as notifications, alerts, or marketing messages. Users can specify the recipient's phone number, sender number, message content, and additional options like encoding and status callback URLs.

Use Case Examples

  1. Sending a notification SMS to a customer with a predefined message.
  2. Automating marketing SMS campaigns by sending personalized messages to multiple recipients.

Properties

Name Meaning
To Destination phone number to which the SMS will be sent. Supports E.164 format or local format with a specified country.
Country Country code used to parse local phone numbers into E.164 format if the number is not in international format.
From Sender phone number. If left empty, the account's default sender number is used.
Message The SMS message content to send. Supports up to 1600 characters with encoding considerations (GSM7 or UCS-2). Longer messages are split into multiple segments.
Additional Fields Optional fields including status callback URL for delivery updates and message encoding (auto-detect, GSM7, UCS-2).

Output

JSON

  • provider - The SMS service provider used (MessageMedia).
  • to - The normalized recipient phone number in E.164 format.
  • from - The sender phone number used or default account number if none specified.
  • message - The content of the sent SMS message.
  • status - The status of the SMS message delivery.
  • providerMessageId - The unique message ID assigned by the provider.
  • error - Any error message returned by the provider if sending failed.
  • meta
    • cost
      * currency - Currency of the cost for sending the message (USD).
      * amount - Cost amount for sending the message (currently 0).
    • encoding - The character encoding detected or used for the message.
    • queuedAt - Timestamp when the message was queued for sending.

Dependencies

  • An API key credential for MessageMedia API

Troubleshooting

  • Ensure phone numbers are in valid E.164 format or provide the correct country code for local numbers to avoid invalid phone number errors.
  • Message length must be between 1 and 1600 characters; exceeding this range will cause an error.
  • If the sender number is invalid or not normalized, the node will throw an error; use a valid sender number or leave empty to use the default.
  • API request failures will throw errors with messages from the provider; check network connectivity and API credentials.

Discussion