Overview
The Toolzz Search node allows you to perform a search query against the Toolzz API, filtering results based on various criteria such as groups, subgroups, specialties, content types, and tags. This node is useful in scenarios where you need to retrieve filtered content or resources from the Toolzz platform, for example:
- Searching for courses or materials by keyword.
- Filtering results by group, subgroup, specialty, content type, or tags.
- Integrating Toolzz content into automated workflows for further processing.
Practical Example:
You could use this node to fetch all courses tagged with "leadership" and belonging to specific groups, then send the results via email or store them in a database.
Properties
| Name | Type | Meaning |
|---|---|---|
| Url | String | The base URL for the request (used in headers). |
| Ambiente | Options | Selects the environment endpoint (e.g., Production: https://gateway.api.toolzz.com.br). |
| Pesquisar | String | The search term to filter results. |
| Grupos | String | Comma-separated list of group IDs to filter results. |
| Sub Grupos | String | Comma-separated list of subgroup IDs to filter results. |
| Especialidades | String | Comma-separated list of specialty IDs to filter results. |
| Tipos De Conteudos | String | Comma-separated list of content type IDs to filter results. |
| Tags | String | Comma-separated list of tags to filter results. |
Output
- The node outputs an array of JSON objects returned by the Toolzz API's
/search/searchendpoint. - Each object in the output array represents a search result matching the provided filters.
- The exact structure of each result depends on the Toolzz API response, but it will be passed through as-is.
Dependencies
- External Service: Requires access to the Toolzz API at
https://gateway.api.toolzz.com.br. - No authentication credentials are specified in the node properties, so ensure the endpoint is accessible without authentication or that your n8n instance/network has the necessary permissions.
Troubleshooting
Common Issues:
- Invalid or empty results: Ensure that the filter values (IDs, tags) are correct and exist in the Toolzz system.
- Connection errors: Make sure the selected environment URL is reachable from your n8n instance.
- API changes: If the Toolzz API changes its response format or required parameters, the node may not function as expected.
Error Messages:
"Request failed with status code 404": The endpoint URL may be incorrect or unavailable."Request failed with status code 400": One or more parameters may be invalid or missing."Network Error": There may be connectivity issues between n8n and the Toolzz API.
How to resolve:
- Double-check all input property values.
- Verify network connectivity and endpoint accessibility.
- Consult Toolzz API documentation for any updates or changes.
Links and References
- Toolzz Platform
- n8n Documentation
- For API details, refer to your organization's Toolzz API documentation or contact Toolzz support.