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 interacts with the Gladly API to perform operations related to conversations. Specifically, the "Redact Content" operation allows users to redact (remove or obscure) sensitive content from a conversation item identified by its unique ID. This is useful in scenarios where personal or confidential information needs to be hidden or deleted from customer support conversations for compliance or privacy reasons.
Practical examples include:
- Automatically redacting credit card numbers or personal identifiers from chat transcripts.
- Removing sensitive information before exporting conversation data.
- Ensuring compliance with data protection regulations by sanitizing stored conversation content.
Properties
| Name | Meaning |
|---|---|
| Item Id | The unique identifier of the conversation item whose content you want to redact. |
Output
The node outputs JSON data representing the result of the redaction operation on the specified conversation item. This typically includes confirmation that the content was successfully redacted or details about the updated conversation item. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint to perform the redaction.
- Network connectivity to the Gladly API service is necessary.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Common issues:
- Invalid or missing Item Id: Ensure the provided conversation item ID exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network errors: Check internet connectivity and API endpoint availability.
- Error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 Not Found may indicate the specified conversation item does not exist.
- 400 Bad Request could mean the input parameters are malformed or incomplete.
- To resolve these, double-check the input properties, ensure proper API credentials are configured, and confirm the conversation item ID is correct.
Links and References
- Gladly API Documentation: https://developer.gladly.com/api-reference/
- n8n Documentation on Credentials: https://docs.n8n.io/credentials/overview/