How to send SMS messages with Sinch

Get started sending SMS notifications with Sinch and Knock.

Knock integrates with Sinch to send SMS notifications to your recipients.

Features

Per environment configuration
Delivery tracking
Knock link tracking
Sandbox mode

Getting started

You can create a new Sinch channel in the dashboard under the Channels and sources page in your account settings. From there, you'll need to configure the channel for each environment you have.

Channel configuration

Configure the following settings per environment. Navigate to Channels and sources in your dashboard account settings and select your Sinch channel. Under Environment configurations, click the environment you'd like to configure to expand its settings, then click "Save changes" when you're done. Expand Advanced for additional options, including overrides and conditions.

Fields marked with an * are required.

API tokenstring*

The API token from Sinch.

Service Plan IDstring*

The Service Plan ID from Sinch.

Sinch regionenum*

The region of your domain. One of AU, BR, CA, EU, US.

Phone numberstring*

The phone number to send messages from. Required when From (under Advanced) is set to Phone number.

Short codestring*

The Sinch short code to send messages from. Required when From (under Advanced) is set to Short code.

Sender IDstring*

The Sinch Sender ID to send messages from. Required when From (under Advanced) is set to Sender ID.

Sandbox modeboolean

Whether to enable sandbox mode for your Sinch channel.

Link trackingboolean

Whether to enable Knock link-click tracking.

Optional Sinch settings

Fromenum

The method used to send your SMS messages. One of Phone number, Short code, or Sender ID. Optional if you have an automatic originator number on your Sinch account.

When configured, the optional payload overrides set here will apply to all SMS notifications sent from this channel in the configured environment. Learn more about SMS channel overrides here.

Payload overridesJSON (string) | liquid

Provide a JSON object to merge into the API payload that is sent to the downstream provider.

Set optional per-environment conditions for this channel. These conditions are evaluated each time a workflow run encounters a step that uses this channel in the configured environment. If the conditions are not met, the step will be skipped.

Recipient data requirements

In order to send an SMS notification you'll need a valid phone_number property set on your recipient.