Actions65
- Custom Field Definitions Actions
- Knowledge Documents Actions
- Media Actions
- Used Tags Actions
- Webhooks Actions
- Sse Actions
- Accounts Actions
- User Management Actions
- Inbox Management Actions
- Conversations Actions
- Conversation Messages Actions
- Bot Actions
- Contacts Actions
Bot → Bot Controller Find All
AI-generatedOverview
This node operation retrieves a paginated list of bots from the Kuantia CRM API. It supports filtering, sorting, selecting specific fields, and including related entities in the response. This is useful for scenarios where you need to fetch and display bot data with customizable query parameters, such as in dashboards, reports, or integrations that require bot information.
Use Case Examples
- Fetch the first page of bots with a limit of 10 items per page, including related company and company accounts data.
- Retrieve bots sorted by creation date in descending order, selecting only id, email, firstName, and lastName fields.
- Apply filters to get bots matching specific criteria and include nested relations using dot notation.
Properties
| Name | Meaning |
|---|---|
| Page | Page number (1-based) for pagination. |
| Limit | Number of items per page for pagination. |
| Relations | Relations to include in the response, supporting nested relations using dot notation. |
| Select | Fields to select in the response to limit the data returned. |
| Sort | Sort configuration to order the results by one or more fields. |
| Filters | Filter conditions as a JSON object to narrow down the results. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
id- Unique identifier of the bot.email- Email address associated with the bot.firstName- First name of the bot.lastName- Last name of the bot.companyaccounts- Nested related accounts of the company included in the response.
Dependencies
- Kuantia CRM API
- API key credential for authentication
Troubleshooting
- Ensure the API credentials are correctly configured and valid to avoid authentication errors.
- Check the network connection and proxy settings if requests fail or time out.
- Verify the JSON format of filters, relations, select, and sort properties to prevent malformed query errors.
- If SSL certificate validation fails, consider enabling the option to ignore SSL issues, but be aware of security risks.