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 run asynchronous agent tasks. Specifically, the "Async" resource with the "Run Agent" operation allows users to trigger an agent process that runs asynchronously and notifies a specified callback URL upon completion.
Common scenarios include:
- Running data enrichment or qualification agents on email addresses or company domains without blocking workflow execution.
- Triggering background processes that require some time to complete, such as lead scoring or content generation.
- Receiving results via webhook callbacks to continue processing once the asynchronous task finishes.
Practical example:
- A user inputs an email and company domain to enrich contact information asynchronously. The node triggers the agent run and provides a callback URL where Octave will send the results once ready.
Properties
| Name | Meaning |
|---|---|
| Callback URL | The URL that Octave will call back upon completion of the asynchronous task. Example: a webhook endpoint. |
| Agent OId | The unique identifier (OId) of the agent to run asynchronously. |
| Inputs (JSON Format) | JSON object containing the inputs for the agent run. The structure depends on the agent type (e.g., email, companyDomain). Example: { "email": "test@example.com", "companyDomain": "example.com" } |
Output
The node outputs JSON data representing the response from the Octave API after initiating the asynchronous agent run. This typically includes confirmation details about the started task.
Since the operation is asynchronous, the actual results are delivered later to the provided callback URL; thus, this node's output mainly confirms the request submission.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Octave V2 API.
- The user must provide a valid callback URL accessible by Octave to receive asynchronous results.
- Network connectivity to Octave's API endpoints and the callback URL endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or unreachable callback URL: Ensure the URL is publicly accessible and correctly formatted.
- Incorrect Agent OId: Verify the agent identifier is correct and corresponds to an existing agent.
- Malformed JSON inputs: Validate the JSON structure matches the expected input schema for the chosen agent.
Error messages:
- API errors returned from Octave may include HTTP status codes and error messages indicating authentication failure, invalid parameters, or server issues.
- Parsing errors if the API response body is malformed or unexpected.
Resolutions:
- Double-check credentials and permissions.
- Validate all input fields before execution.
- Monitor network connectivity and endpoint availability.
- Use the node's "Continue On Fail" option to handle errors gracefully within workflows.
Links and References
- Octave API Documentation (general reference for API endpoints and agent definitions)
- Webhook best practices for receiving asynchronous callbacks
- JSON validation tools for preparing input data