Algolia

Overview

The Algolia "Search" node with the "Search" operation allows sending multiple search queries to one or more indices in a single request. This is useful when you want to perform complex searches across different datasets or apply different filters and parameters for each query within the same workflow execution.

Common scenarios include:

• Searching multiple indices simultaneously, such as separate indices for products and marketing content.
• Running multiple filtered or customized searches on the same index to retrieve diverse results.
• Implementing advanced search strategies like stopping early if enough matches are found.

For example, you might use this node to search a product catalog and a blog index at once, or to run several queries with different filters to find the best matching results quickly.

Properties

Output

The node outputs the JSON response from Algolia's multi-query search API. The output contains an array of results corresponding to each search query sent. Each result includes typical Algolia search response fields such as:

• hits: Array of matched records for the query.
• nbHits: Number of hits returned.
• page, hitsPerPage: Pagination details.
• Other metadata related to facets, ranking info, and analytics depending on the query parameters.

No binary data is output by this node.

Dependencies

• Requires an Algolia application ID and an API key credential configured in n8n.
• The node sends requests to the Algolia REST API endpoint based on the provided credentials.
• No additional external dependencies.

Troubleshooting

• Authentication errors: Ensure that the API key credential has the necessary permissions to perform search queries.
• Empty results: Verify that the indices and queries are correctly specified and that the indices contain data.
• Rate limits: Algolia enforces rate limits; hitting these may cause errors. Consider optimizing queries or upgrading your plan.
• Invalid parameters: Make sure the search parameters conform to Algolia's API specifications, especially for complex filters and facet settings.
• Strategy misuse: Using stopIfEnoughMatches requires understanding that queries will stop early; ensure this behavior fits your use case.

Links and References

• Algolia Multi-Query Search API
• Algolia Search Parameters
• Algolia Official Documentation

This summary focuses on the "Search" resource and "Search" operation, describing its purpose, input properties, output structure, dependencies, and common troubleshooting points based on static analysis of the provided source code and parameter definitions.