Actions36
- 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 manage various resources such as accounts, contacts, conversations, messages, inboxes, canned responses, webhooks, teams, and labels. Specifically, for the Team resource with the Get Many operation, it retrieves a list of teams associated with a Chatwoot account.
Use cases include:
- Fetching all teams in a Chatwoot account to display or process team data.
- Automating workflows that require team information from Chatwoot.
- Integrating team data into other systems or dashboards.
Example: You want to retrieve all support teams configured in your Chatwoot account to assign conversations dynamically based on team availability.
Properties
| Name | Meaning |
|---|---|
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Whether to output detailed request and response logs to the console for debugging. |
These properties control error handling behavior and logging verbosity during execution.
Output
The node outputs JSON data representing the teams retrieved from the Chatwoot API. For the "Get Many" operation on the Team resource, the output is an array where each item contains the JSON representation of a single team object as returned by Chatwoot.
The structure corresponds directly to the API's team payload, typically including fields like team ID, name, description, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Chatwoot API.
- The node expects the Chatwoot account ID and base URL to be provided via credentials.
- Network access to the Chatwoot instance is necessary.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Incorrect account ID or base URL in credentials may lead to failed requests.
- Network connectivity problems can prevent API calls.
- Error messages:
- HTTP request failures will throw errors with details logged if debug logging is enabled.
- JSON parsing errors are unlikely here since this operation only performs GET requests without custom JSON input.
- Resolutions:
- Verify API key and account ID correctness.
- Enable debug logging to see detailed request URLs and headers.
- Check network connectivity and firewall settings.
- Ensure the Chatwoot API endpoint is reachable and operational.