RingCentral

undefined

Detail	Value
Category	Communication
Base URL	https://platform.ringcentral.com/restapi
Authentication	OAuth2
Endpoints	7
Connector key	ringcentral

Using RingCentral in a workflow

1. Go to Connections and click New Connection.
2. Pick RingCentral 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 SMS
GET	List Call Log
GET	Make RingOut Call
GET	List Extensions
GET	Create Meeting
GET	List Contacts
GET	Get Presence

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

GET

Send SMS

Detail	Value
Operation ID	send_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 RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select send_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 RingCentral API reference.

GET

List Call Log

Detail	Value
Operation ID	list_call_log_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 RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select list_call_log_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 RingCentral API reference.

GET

Make RingOut Call

Detail	Value
Operation ID	make_ringout_call_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 RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select make_ringout_call_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 RingCentral API reference.

GET

List Extensions

Detail	Value
Operation ID	list_extensions_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 RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select list_extensions_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 RingCentral API reference.

GET

Create Meeting

Detail	Value
Operation ID	create_meeting_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 RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select create_meeting_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 RingCentral API reference.

GET

List Contacts

Detail	Value
Operation ID	list_contacts_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select list_contacts_5.
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 RingCentral API reference.

GET

Get Presence

Detail	Value
Operation ID	get_presence_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your RingCentral connection from the Connection dropdown.
3. In the Operation dropdown, select get_presence_6.
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 RingCentral API reference.