Actions26
- Agent Actions
- API Key Actions
- Async Actions
- Headless Actions
- Persona Actions
- Playbook Actions
- Product Actions
- Reference Actions
- Use Case Actions
Overview
The "Agent - Run Sequence" operation in this node allows users to run a predefined sequence using an agent identified by its OId (Object ID). This operation is useful for automating outreach or engagement workflows, such as sending personalized email sequences or multi-step campaigns targeted at specific contacts or companies.
Typical use cases include:
- Running sales or marketing sequences tailored to a contact's profile.
- Automating follow-ups based on company or person data.
- Generating content or messages dynamically within a sequence context.
For example, a user might select an agent representing a sales bot and provide details about a prospect (email, company domain, job title) to run a customized outreach sequence that adapts messaging based on the input data.
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 via expression. |
| Company Domain | Optional. The domain name of the company related to the sequence (e.g., example.com). |
| Company Name | Optional. The name of the company associated with the target person. |
| Optional. The email address of the person involved in the sequence. | |
| 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. |
| Language | Optional. Language code (such as "en" for English or "es" for Spanish) to specify the language of the sequence. |
| Output Format | Optional. Desired output format of the sequence result. Options are: "Text" or "HTML". Default is "Text". |
| Runtime Context (JSON) | Optional. Additional JSON object providing runtime context to customize the sequence execution. |
| Runtime Instructions (JSON) | Optional. Additional JSON instructions to guide or modify the behavior of the sequence during runtime. |
Output
The node outputs an array of JSON objects representing the results of running the sequence. Each output item typically contains the generated content or responses produced by the agent sequence, formatted according to the selected output format (text or HTML).
If binary data were involved (not indicated here), it would represent files or attachments generated by the sequence, but this operation focuses on JSON/textual output.
Dependencies
- Requires an API key credential for authenticating with the Octave V2 API.
- The node depends on the Octave service backend to execute agent sequences.
- Proper configuration of the API key credential in n8n is necessary.
- The "Agent OId" must correspond to a valid agent configured in the Octave system.
Troubleshooting
- Invalid Agent OId: If the specified agent ID does not exist or is incorrect, the node will throw an error. Verify the agent selection or ID expression.
- API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Malformed JSON in Runtime Context/Instructions: Providing invalid JSON in these optional fields can cause parsing errors. Validate JSON syntax before input.
- Empty or Unexpected Output: If the sequence runs but returns no data, check that the agent is properly configured and that input properties (like email or company domain) are correct and sufficient for the sequence logic.
- Continue On Fail Behavior: If enabled, the node captures errors per item and continues processing others; otherwise, it stops on the first failure.
Links and References
- Octave API Documentation (hypothetical link)
- n8n Expressions Documentation
- Octave Agent Sequences Guide (hypothetical link)