Overview
This node provides an interface to the Explorium API, specifically supporting multiple operations including an Autocomplete operation. The Autocomplete operation fetches autocomplete suggestions for a specified field based on a search query. This is useful when you want to provide dynamic suggestions or filter options in workflows, such as suggesting industry categories, technologies, locations, or company sizes while building data enrichment or prospecting automations.
Practical examples:
- Suggesting Google business categories as a user types a partial category name.
- Providing technology stack suggestions based on partial input.
- Offering location names dynamically filtered by user input.
Properties
| Name | Meaning |
|---|---|
| Field | The field to get autocomplete suggestions for. Options: Google Category, Industry, Technology, Location, Company Size. Default is Google Category. |
| Query | The search term string used to fetch autocomplete suggestions (e.g., "software"). |
| Advanced JSON Input | Boolean flag to toggle between using form fields or direct JSON input for parameters. |
| JSON Input | When using advanced JSON input, this JSON object specifies the field and query parameters directly. |
Output
The output is a JSON object containing the autocomplete suggestions returned from the Explorium API endpoint /v1/businesses/autocomplete. The structure depends on the API response but generally includes a list of suggested values relevant to the requested field and query.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Explorium API.
- The node makes HTTP GET requests to
https://api.explorium.ai/v1/businesses/autocomplete. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
- Empty or invalid JSON Input: If using advanced JSON input, ensure the JSON is valid and not empty; otherwise, the node throws an error.
- Unknown operation error: Selecting an unsupported operation will cause an error.
- API request failures: Network issues or invalid API credentials can cause HTTP request errors.
- Missing required parameters: Both
fieldandqueryare required; missing these will result in errors.
To resolve:
- Validate JSON input format if using advanced mode.
- Confirm API key credential is correctly set up.
- Ensure required parameters are provided.
- Check network connectivity and API service status.
Links and References
- Explorium API Documentation (for detailed API usage and field definitions)
- n8n documentation on Creating Custom Nodes