Octave icon

Octave

Interact with the Octave V2 API

Overview

The "Agent - Qualify Company" operation allows users to evaluate or qualify a company based on its domain and optional additional information by running a specified agent. This node is useful in scenarios such as lead qualification, market research, or sales prospecting where automated assessment of companies is needed to determine their suitability or fit according to custom criteria.

For example, a sales team could use this node to automatically qualify incoming leads by providing the company's domain and optionally its name, along with extra context or inputs that influence the qualification logic defined in the agent. The agent then processes this data and returns qualification results that can be used downstream in workflows.

Properties

Name Meaning
Agent OId Name or ID The unique identifier (OId) of the agent to run for qualifying the company. Choose from a list or specify an ID via expression.
Company Domain The domain name of the company to qualify (e.g., example.com). Required to identify the target company.
Company Name Optional name of the company to provide additional identification or context.
Runtime Context (JSON) Optional JSON object containing additional runtime context to pass to the agent during execution.
Additional Inputs (JSON) Optional JSON object for any other inputs the agent might accept, such as specific qualification criteria (e.g., revenue > 10M).

Output

The node outputs JSON data representing the result of the company qualification performed by the selected agent. The exact structure depends on the agent's implementation but typically includes qualification status, scores, or metadata about the company based on the input parameters.

If the agent supports binary data output, it would be summarized accordingly; however, no explicit binary output handling is indicated in the provided code snippet.

Dependencies

  • Requires an API key credential for authenticating with the Octave V2 API.
  • Depends on the Octave platform's backend services to execute the agent logic.
  • The node uses internal methods to load available agents dynamically for selection.
  • No additional external dependencies are indicated beyond the Octave API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing agent OId: Ensure the agent ID is correctly selected or specified.
    • Incorrect company domain format: Validate the domain string is properly formatted (e.g., no protocol prefix).
    • Malformed JSON in runtimeContext or additionalInputsJson: Verify JSON syntax correctness.
    • API authentication errors: Confirm the API key credential is valid and has necessary permissions.
  • Error Messages:

    • Errors thrown by the API will be captured and included in the output under an error field.
    • If the API response body cannot be parsed as JSON, a parse error message will be added.
    • When continueOnFail is enabled, errors do not stop execution but are returned as part of the output for each failed item.

Links and References

Discussion