How to list ringcentral call log in RingCentral

List RingCentral Call Log 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
Direction direction	options	Optional	–
Call Type type	options	Optional	–
From Date/Time (ISO 8601) dateFrom	string	Optional	2026-01-01T00:00:00.000Z
Per Page perPage	number	Optional	Max 1000.

Sample request

{
  "direction": "{{trigger.direction}}",
  "type": "{{trigger.type}}",
  "dateFrom": "2026-01-01T00:00:00.000Z",
  "perPage": "{{trigger.perPage}}"
}

Returns

{
  "paging": {
    "totalElements": 1
  },
  "records": [
    {
      "id": "abc123",
      "to": {
        "phoneNumber": "+15559876543"
      },
      "from": {
        "phoneNumber": "+15551234567"
      },
      "result": "Accepted",
      "duration": 42,
      "direction": "Inbound",
      "startTime": "2026-01-15T12:00:00.000Z"
    }
  ]
}

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

FAQ

Questions about List RingCentral Call Log.

What does the List RingCentral Call Log action do in RingCentral?

Paginated call history with filters. For "yesterday's call summary" reporting and for compliance audit workflows.

What inputs does List RingCentral Call Log require?

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

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

More actions