How to list ringcentral extensions in RingCentral

List RingCentral Extensions in RingCentral — start free

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
Status status	options	Optional	–
Extension Type type	options	Optional	–
Per Page perPage	number	Optional	–

Sample request

{
  "status": "{{trigger.status}}",
  "type": "{{trigger.type}}",
  "perPage": "{{trigger.perPage}}"
}

Returns

{
  "paging": {
    "totalElements": 1
  },
  "records": [
    {
      "id": 101,
      "name": "Jane Doe",
      "type": "User",
      "status": "Enabled",
      "contact": {
        "email": "jane@acme.com"
      },
      "extensionNumber": "101"
    }
  ]
}

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

FAQ

Questions about List RingCentral Extensions.

What does the List RingCentral Extensions action do in RingCentral?

Returns the account's extensions (users with phone numbers). For resolving extension IDs in routing workflows.

What inputs does List RingCentral Extensions require?

List RingCentral Extensions has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List RingCentral Extensions support batch operations?

Yes. Run List RingCentral Extensions inside a Loop node to process arrays. TinyCommand handles RingCentral's rate limits automatically so you don't have to throttle manually.

More actions