Actions26
- Agent Actions
- API Key Actions
- Async Actions
- Headless Actions
- Persona Actions
- Playbook Actions
- Product Actions
- Reference Actions
- Use Case Actions
Overview
This node integrates with the Octave V2 API to enrich personal data using an "Agent" resource. Specifically, the "Enrich Person" operation allows users to provide partial information about a person (such as email, name, job title, LinkedIn profile, or company details) and receive enriched data about that individual. This is useful in scenarios like lead generation, customer profiling, or enhancing CRM records with additional insights.
For example, a marketing automation workflow could use this node to enrich contact details before sending personalized campaigns, or a sales team might use it to gather more comprehensive information about prospects.
Properties
| Name | Meaning |
|---|---|
| Agent OId Name or ID | The identifier of the agent to run. Select from a list of available agents or specify an ID via expression. |
| Company Domain | Optional. The domain of the company associated with the person (e.g., example.com). |
| Company Name | Optional. The name of the company related to the person. |
| Optional. The email address of the person to enrich. | |
| First Name | Optional. The first name of the person. |
| Job Title | Optional. The job title of the person. |
| LinkedIn Profile URL | Optional. The LinkedIn profile URL of the person. |
| Runtime Context (JSON) | Optional. Additional JSON context to provide extra information for enrichment. |
Output
The node outputs JSON data containing the enriched person information returned by the Octave API. This typically includes detailed personal and professional attributes inferred or retrieved based on the input properties provided.
If the node supports binary data output, it would represent attachments or files related to the enriched person data, but this is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Octave V2 API.
- The node depends on the Octave API service being accessible.
- No other external dependencies are explicitly required.
- The node uses internal methods to load options dynamically (e.g., available agents).
Troubleshooting
- Common issues:
- Providing insufficient or incorrect input data may result in incomplete or no enrichment results.
- Network or authentication errors if the API key is invalid or the Octave API is unreachable.
- Error messages:
- Errors thrown by the API will be caught and can include the API response body for debugging.
- Parsing errors of the API response body are handled gracefully with an explanatory message.
- Resolution tips:
- Verify the API key credential is correctly configured.
- Ensure the agent ID is valid and selected properly.
- Provide at least some identifying information (email, name, or LinkedIn URL) to improve enrichment success.
Links and References
- Octave API Documentation (hypothetical link, replace with actual)
- n8n Expressions Documentation – for using expressions in property fields