Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node operation updates the call recording status of a specific agent in a customer service or call center environment. It is useful for scenarios where you need to programmatically control or track whether an agent's call is being recorded, such as compliance monitoring, quality assurance, or real-time call management.
For example, if an agent starts or stops recording a call, this node can update that status in the system. It can also associate the recording status with a particular customer and conversation item if the agent is currently on a call.
Properties
| Name | Meaning |
|---|---|
| Agent Id | The unique identifier of the agent whose call recording status is being updated. |
| Customer Id | The unique identifier of the customer involved in the call, if the agent is currently on a call. |
| Conversation Item Id | The unique identifier of the conversation item related to the call, if the agent is on a call. |
| Recording | Boolean flag indicating whether the call is currently being recorded (true) or not (false). |
Output
The node outputs JSON data reflecting the result of the update operation. This typically includes confirmation of the updated recording status and may include details about the agent, customer, and conversation item involved.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the Gladly API endpoint configured with appropriate authentication (e.g., an API key credential).
- The base URL for API requests is set to
https://petstore3.swagger.io/api/v3in the bundled code, which is likely a placeholder; in production, it should be replaced with the actual Gladly API endpoint. - Proper credentials must be configured in n8n to authenticate API requests.
Troubleshooting
- Invalid Agent Id: If the provided agent ID does not exist or is malformed, the API may return an error. Verify the agent ID before making the request.
- Agent Not on Call: Omitting
Customer IdandConversation Item Idwhen the agent is not on a call is required. Including them incorrectly might cause errors. - Authentication Errors: Ensure that the API key or authentication token is correctly configured and has sufficient permissions.
- API Endpoint Issues: The default base URL points to a Swagger Petstore demo URL; ensure the correct Gladly API URL is used in production.
- Boolean Value Handling: The
Recordingproperty must be a boolean; passing other types may cause unexpected behavior.
Links and References
- Gladly API Documentation (replace with actual API docs)
- n8n HTTP Request Node Documentation for understanding how API calls are made within n8n nodes.