Delete Recording
plivo.delete_recording
ActionVoice & SMSconnection required
Calls the Plivo API with the connection's credentials.
Delete a stored call recording and the audio file behind it.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Plivo
- Secret shape
- {"username": "<Auth ID>", "password": "<Auth Token>"}
- Config it needs
- auth_id, src, answer_url, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
recording_id The identifier of the recording to delete. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True when Plivo accepted the deletion. | boolean | — |
recording_id The recording that was deleted. | string | — |
message Plivo's acknowledgement text, such as 'call transfered'. | string | — |
api_id Plivo's identifier for this API request. | string | — |
response The acknowledgement exactly as Plivo returned it. | object | — |
{
"api_id": "",
"deleted": false,
"message": "",
"recording_id": "",
"response": {}
}See Delete Recording run in a workflow.
In a technical demo we add the Plivo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.