Actions26
- Agent Actions
- API Key Actions
- Async Actions
- Headless Actions
- Persona Actions
- Playbook Actions
- Product Actions
- Reference Actions
- Use Case Actions
Overview
The "Agent - Qualify Person" operation in this node interacts with the Octave V2 API to assess or qualify an individual person based on various input attributes. This operation is useful for sales, marketing, or recruitment automation workflows where you want to evaluate a person's fit or qualification status using data such as their email, job title, company information, and LinkedIn profile.
Typical use cases include:
- Automatically qualifying leads by verifying their role and relevance within a company.
- Enriching contact data with qualification insights before further processing.
- Integrating qualification logic into CRM or outreach automation pipelines.
For example, you might provide the agent ID along with a person's email and job title, and the node will return qualification details that help decide if this person should be pursued further.
Properties
| Name | Meaning |
|---|---|
| Agent OId Name or ID | The unique identifier of the agent to run. Choose from a list or specify an ID via expression. |
| Company Domain | Optional. The domain name of the company (e.g., example.com) associated with the person. |
| Company Name | Optional. The name of the company related to the person. |
| Optional. The email address of the person to qualify. | |
| First Name | Optional. The first name of the person to qualify. |
| Job Title | Optional. The job title of the person to qualify. |
| LinkedIn Profile URL | Optional. The LinkedIn profile URL of the person to qualify. |
| Runtime Context (JSON) | Optional. Additional JSON context to provide runtime parameters or metadata for the qualification process. |
| Additional Inputs (JSON) | Optional. A JSON object containing any other inputs the agent might accept, e.g., qualification questions. |
Output
The node outputs JSON data representing the qualification results returned by the Octave API for the specified person. This typically includes detailed qualification insights, scoring, or metadata about the person’s suitability or status according to the agent's logic.
If the node supports binary data output, it would represent additional content such as reports or documents generated during the qualification, but this operation primarily focuses on JSON structured data.
Dependencies
- Requires an active connection to the Octave V2 API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node dynamically loads available agents via a method to populate the "Agent OId" options.
Troubleshooting
Common issues:
- Missing or invalid agent ID: Ensure the agent ID is correctly selected or provided.
- Invalid or incomplete person data: Supplying minimal identifying information may lead to insufficient qualification results.
- API authentication errors: Verify that the API key credential is valid and has necessary permissions.
- JSON parsing errors in additional inputs: Make sure any JSON entered in "Runtime Context" or "Additional Inputs" is well-formed.
Error messages:
- Errors from the API are caught and included in the output under an error field if "Continue On Fail" is enabled.
- Parsing errors for API responses are reported with a specific message indicating failure to parse the response body.
- Network or authorization failures will throw exceptions unless handled by the node's fail settings.
Links and References
- Octave API Documentation (hypothetical link)
- n8n Expressions Documentation
- JSON Syntax Guide