Get RingCentral Recording: RingCentral action

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
Recording ID recordingId	string	Required	12345

Sample request

{
  "recordingId": "12345"
}

Returns

{
  "id": "12345",
  "type": "Automatic",
  "duration": 120,
  "contentUri": "https://media.ringcentral.com/restapi/v1.0/account/~/recording/12345/content",
  "contentType": "audio/mpeg"
}

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

FAQ

Questions about Get RingCentral Recording.

What does the Get RingCentral Recording action do in RingCentral?

Returns the recording audio file by call ID. For "post-call → transcribe + AI-summarise → log to CRM" workflows.

What inputs does Get RingCentral Recording require?

Required: Recording ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get RingCentral Recording support batch operations?

Yes. Run Get RingCentral Recording inside a Loop node to process arrays. Tiny Command handles RingCentral's rate limits automatically so you don't have to throttle manually.

More actions