Actions26
- Agent Actions
- API Key Actions
- Async Actions
- Headless Actions
- Persona Actions
- Playbook Actions
- Product Actions
- Reference Actions
- Use Case Actions
Overview
The "Agent - Enrich Company" operation in this node allows users to enrich company data by providing a company domain and optionally a company name. It uses a specified agent (selected by its OId) to perform the enrichment, potentially adding valuable information about the company based on the domain. This is useful for scenarios such as lead enrichment, market research, or enhancing CRM records with additional company details.
For example, a marketing automation workflow could use this node to automatically fetch detailed company profiles from just a domain name before sending personalized campaigns.
Properties
| Name | Meaning |
|---|---|
| Agent OId Name or ID | The unique identifier of the agent to run. Choose from a list of available agents or specify an ID directly. |
| Company Domain | The domain name of the company to enrich (e.g., example.com). This is required to identify the target company. |
| Company Name | Optional. The name of the company to assist in enrichment, if known. |
| Runtime Context (JSON) | Additional JSON-formatted context data passed to the agent at runtime to customize or influence the enrichment process. |
Output
The node outputs enriched company data in the json field of the output items. This typically includes detailed information about the company derived from the domain and optional name, as processed by the selected agent. The exact structure depends on the agent's response but generally contains company attributes like industry, size, location, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Octave V2 API.
- Depends on the availability of configured agents within the Octave platform; the user must select a valid agent OId.
- The node internally calls a router function that dispatches the request to the appropriate agent operation handler.
Troubleshooting
Common issues:
- Invalid or missing agent OId: Ensure the agent is correctly selected or the ID is valid.
- Incorrect or malformed company domain: Validate the domain format (e.g., no spaces, proper domain syntax).
- API authentication errors: Verify that the API key credential is set up correctly and has necessary permissions.
- Network or API downtime: Check connectivity and Octave service status.
Error messages:
- Errors returned from the API are captured and included in the output under an error object.
- Parsing errors of API responses may occur; these are noted with a parse error message.
- If the node is set to continue on failure, errors will be output as JSON objects instead of stopping execution.
Links and References
- Octave API Documentation (hypothetical link)
- n8n Expressions Documentation – for using expressions in property fields
- General best practices for company data enrichment and lead management workflows