Short answer: Drop the "RingCentral → List RingCentral Call Log" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
{"direction": "{{trigger.direction}}","type": "{{trigger.type}}","dateFrom": "2026-01-01T00:00:00.000Z","perPage": "{{trigger.perPage}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.