Short answer: You can get ringcentral recording in RingCentral by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the RingCentral Get RingCentral Recording action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
{"recordingId": "12345"}
{"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.
Any of these apps can fire this action as part of a workflow.