Actions113
- Accounts Actions
- Account Users 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
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
This node interacts with the ChatWoot API to retrieve canned responses associated with a specific account. The "Get Account Canned Response" operation fetches predefined message templates (canned responses) that can be used for quick replies in customer support scenarios.
Common use cases include:
- Automating retrieval of canned responses to display or process within workflows.
- Integrating ChatWoot canned responses into other systems or messaging platforms.
- Managing and syncing canned responses across multiple tools.
For example, a support team could use this node to pull all canned responses for an account and then filter or update them as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to fetch canned responses from |
Output
The node outputs JSON data containing the list of canned responses retrieved from the specified account. Each item typically includes details such as the response text, identifier, and metadata related to the canned response.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the credentials.
- Uses the ChatWoot REST API endpoint for fetching canned responses.
Troubleshooting
- Invalid Account Id: If the provided account ID does not exist or is incorrect, the API may return an error or empty result. Verify the account ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- Network Issues: Connectivity problems to the ChatWoot server will prevent data retrieval. Check network access and firewall settings.
- API Rate Limits: Excessive requests might trigger rate limiting by ChatWoot. Implement retry logic or reduce request frequency if needed.