Actions115
- Teams Actions
- Account Users Actions
- Custom Attributes Actions
- Contacts Actions
- Conversation Labels Actions
- Reports Actions
- Accounts Actions
- Contact Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Messages Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Inboxes Actions
- Integrations Actions
- Profile Actions
- Custom Filters Actions
- Webhooks Actions
Overview
This node operation deletes a specific canned response from an account in the Konverte Digital system. It is useful for managing and cleaning up canned responses that are no longer needed or relevant. For example, if a canned response is outdated or incorrect, this operation can remove it from the account to maintain an organized and up-to-date set of responses.
Use Case Examples
- Deleting a canned response by specifying the account ID and the canned response ID to remove obsolete or incorrect responses from the account.
- Automating the cleanup of canned responses in bulk by integrating this node in workflows that manage account data.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account from which the canned response will be deleted. |
| Id | The ID of the canned response to be deleted from the specified account. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to control how the API request is made. |
Output
JSON
success- Indicates whether the canned response was successfully deleted.message- Additional information or confirmation message about the deletion operation.
Dependencies
- Requires an API key credential for authentication with the Konverte Digital API.
Troubleshooting
- Ensure the account ID and canned response ID are correct and exist in the system to avoid 'not found' errors.
- Check network connectivity and proxy settings if requests fail to reach the API.
- If SSL certificate validation fails, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
- Timeout errors may occur if the server is slow to respond; adjust the timeout setting accordingly.