Actions35
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Chatwoot API to perform various operations on different resources such as accounts, contacts, conversations, messages, inboxes, canned responses, webhooks, teams, and labels. Specifically, for the Account resource with the Get operation, it retrieves detailed information about a specific account by its numeric ID.
Common scenarios where this node is beneficial include:
- Fetching account details to display or use in workflows.
- Automating customer support processes by retrieving account info dynamically.
- Integrating Chatwoot account data into other systems or dashboards.
Example:
You want to get details of an account with ID 123 to verify its status or settings before proceeding with further automation steps.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric ID of the account to retrieve details for (required). |
| Continue on Fail | Whether to continue executing subsequent items if this operation fails. |
Output
The output contains a JSON object representing the full details of the requested account as returned by the Chatwoot API. This typically includes all account-related fields such as name, settings, status, and metadata.
Output example structure (simplified):
{
"id": 123,
"name": "Example Account",
"email": "contact@example.com",
"status": "active",
"created_at": "2023-01-01T00:00:00Z",
...
}
No binary data output is produced by this operation.
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.
- Network access to the Chatwoot API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Account ID parameter will cause the request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the Chatwoot API.
Error messages:
"404 Not Found": The specified account ID does not exist."401 Unauthorized": Authentication failed due to invalid API key."400 Bad Request": Malformed request, possibly due to invalid parameters.
Resolutions:
- Verify the Account ID is correct and exists in Chatwoot.
- Ensure the API key credential is valid and has appropriate permissions.
- Check network connectivity and firewall settings.