Sinch

undefined

Detail	Value
Category	Communication
Base URL	https://us.sms.api.sinch.com/xms/v1/{service_plan_id}
Authentication	Bearer Token
Endpoints	5
Connector key	sinch

Using Sinch in a workflow

1. Go to Connections and click New Connection.
2. Pick Sinch from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET	Send Batch SMS
GET	List Batches
GET	Get Delivery Report
GET	List Inbound Messages
GET	Manage Groups

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Send Batch SMS

Detail	Value
Operation ID	send_batch_sms_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sinch connection from the Connection dropdown.
3. In the Operation dropdown, select send_batch_sms_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sinch API reference.

GET

List Batches

Detail	Value
Operation ID	list_batches_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sinch connection from the Connection dropdown.
3. In the Operation dropdown, select list_batches_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sinch API reference.

GET

Get Delivery Report

Detail	Value
Operation ID	get_delivery_report_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sinch connection from the Connection dropdown.
3. In the Operation dropdown, select get_delivery_report_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sinch API reference.

GET

List Inbound Messages

Detail	Value
Operation ID	list_inbound_messages_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sinch connection from the Connection dropdown.
3. In the Operation dropdown, select list_inbound_messages_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sinch API reference.

GET

Manage Groups

Detail	Value
Operation ID	manage_groups_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sinch connection from the Connection dropdown.
3. In the Operation dropdown, select manage_groups_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sinch API reference.