Resources · Zapier integration

Octave Zapier integrationAutomate Octave with Zapier.

The Octave Zapier integration gives you 0 triggers, 66 actions and 26 searches. Octave never starts a Zap on its own: another app always does that part, then Octave enriches, qualifies, writes or looks up what your sales team needs.

See the 92 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Octave Zapier integration actually does

Octave is an AI context engine for B2B sales and marketing teams: it researches, qualifies, enriches and drafts messages through agents you configure. The Zapier integration lets another tool hand a company or a person to those agents, then pass the answer to the next step, without anyone copying data by hand.

Three results come back again and again. An enriched account: a domain arrives from a form or a sheet, Enrich Company fills in the research, and Qualify Company says whether it fits a product or segment. A ready-to-send sequence: Run Sequence drafts the emails for a person, which the next step drops into your outreach tool. A knowledge base that feeds itself: Create Resource pushes a document, a URL or a Drive file into Octave, so every agent reads the latest material.

What Zapier does not do here matters as much. Octave exposes no trigger at all, so nothing that happens inside Octave can start a Zap: the first step always belongs to another app, a CRM, a form or a spreadsheet. The long jobs (Run Agent Asynchronously, Run Workflow) answer later, through a callback address or a status check, and a Zap does not wait for them by itself.

If you compare platforms, the Octave Make integration page is the counterpart of this one, and Make vs Zapier is the place to weigh the two tools.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Octave has none, so the trigger always comes from another app.
Action
What the Zap does once started: the step that creates, updates, runs or sends something for you in Octave.
Task
The unit Zapier bills: one action that completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer set by your plan. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already stored in an app, so the following steps can reuse what it found.
Cost

What an Octave Zap really costs

Octave is not a premium app: it works from the free plan. The bill is counted in tasks, and only a successful action counts.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan stepsOne trigger and one action
  • Premium appNo, Octave works on every plan
  • Trigger cost0 task

The trigger costs nothing, however often Zapier checks the other app. Each Octave action that goes through counts one task, so enriching then qualifying a company costs two. A failed action is not billed. The free plan gives 100 tasks a month but stops at two steps, one trigger and one action. Add a filter, a search step or a second Octave action and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect your Octave account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your Octave account linked once to Zapier, then reused by every step that talks to Octave.

  2. 02

    Pick Octave

    Type Octave in the search box of the dialog, select it, then click Add connection. A new tab opens on the Octave side. You need an Octave account before this point, Zapier does not create one.

  3. 03

    Sign in and grant access

    Sign in to Octave in that tab and allow Zapier to access the account. Anything you want the Zap to touch but do not own yourself needs read or write access granted to you in Octave first.

First Zap

Your first Octave Zap: enrich and qualify new accounts

GoalEach new company domain added to a sheet gets enriched, then qualified, by Octave.

  1. 01

    Build: pick the starting app

    Create a Zap and choose the app that starts it, here a spreadsheet where new accounts land. Octave cannot be this first step, it has no trigger.

  2. 02

    Test the trigger on real data

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real row instead of a guess.

  3. 03

    Add the filter

    Add a filter so the Zap goes on only when the domain column is filled. Pick a text rule for a text column, otherwise the filter never passes. This step makes the Zap multi-step.

  4. 04

    Add Enrich Company, then Qualify Company

    Add Enrich Company, choose your enrich agent and map the domain. Then add Qualify Company with your qualify agent. Each one counts a task when it succeeds.

  5. 05

    Test each step, then publish

    Run each step once and read what Octave sends back before going further. When the answers look right, click Publish to switch the Zap on.

Actions

The 66 Octave actions

Octave gives you 66 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Build Workspace

Action

In Zapier“Generate and build a Workspace”

Sets up a full Octave workspace from three inputs: a workspace name, an offering name and what makes that offering stand out. You can also pull existing users into it.

When to use it
a new business line signs off on its positioning, and the workspace should exist the moment the form is submitted.
Watch out
the value proposition is free text, so a vague sentence produces a vague workspace.
2

Call Prep

Action

In Zapier“Generate call prep content including discovery questions, call scripts, and objection handling”

Runs one of your call prep agents and returns discovery questions, a call script and answers to likely objections, ready to read before the meeting.

When to use it
a demo gets booked in your calendar tool and the rep should find the brief attached to the deal before dialing.
Watch out
the call prep agent must already exist in Octave, the action does not build one.
3

Create Agent

Action

In Zapier“Create a new agent in your workspace”

Adds a new agent to your workspace with a name, a description and a type. Switches let you turn on brand voice, web search, CRM activity or the high-effort mode.

When to use it
an ops team spins up the same agent for every new market from a request form.
Watch out
the type is required and decides what the agent can do afterwards.
4

Delete Agent

Action

In Zapier“Deletes an agent by OId”

Removes an agent for good, identified by its OId, the identifier Octave attaches to every object.

When to use it
a campaign closes in your project tool and its dedicated agents should disappear with it, so nobody keeps running them by mistake.
Watch out
any other Zap that still calls this agent starts failing on its next run.
5

Enrich Company

Action

In Zapier“Enrich a company using an Octave agent”

Hands a company domain, such as example.com, to your enrich company agent and returns the research it gathered on that account.

When to use it
a new account appears in your CRM with nothing but a website, and the next step should fill in the record.
Watch out
the field expects a bare domain, so map the domain column, not a full page address.
6

Enrich Person

Action

In Zapier“Enrich a person using an Octave agent”

Sends a contact to your enrich person agent and gets back what it found about that individual, ready to map into later steps.

When to use it
someone fills in a demo request and sales wants their role and background before the first reply goes out.
Watch out
pick the right enrich person agent, the field is required and lists only agents of that type.
7

Generate Content

Action

In Zapier“Generate content for a person using an Octave agent”

Asks a content agent to write a piece for a given person. The list of agents also shows your running experiments, so a test version can do the writing.

When to use it
a lead reaches a new lifecycle stage and needs a tailored follow-up message drafted.
Watch out
each generation that succeeds counts one task, even if nobody sends the text.
8

Qualify Company

Action

In Zapier“Determine if a company is qualified for a given Product and/or Segment”

Lets a qualify company agent judge whether an account fits a given product, a given segment, or both, and returns that verdict.

When to use it
right after enrichment, to route good-fit accounts to sales and leave the rest in nurture.
Watch out
the answer is only as sharp as the products and segments you described in Octave.
9

Qualify Person

Action

In Zapier“Determine if a person is qualified for a given Product, Persona, and/or Segment”

Checks one contact against a product, a persona and a segment in any combination, through your qualify person agent.

When to use it
a webinar sign-up should reach a rep only if the attendee matches the buyer persona you sell to.
Watch out
a persona that was never defined in Octave gives the agent nothing to compare against.
10

Run Context Agent

Action

In Zapier“Fetch context using a Context-type agent. Useful for enriching records with curated research or notes.”

Calls an agent of the Context type to fetch curated research or notes, handy to attach background to a record.

When to use it
an opportunity moves to the proposal stage and the deal page should carry the account context your team curated.
Watch out
only agents of the Context type are accepted in the required field.
11

Run Prospector

Action

In Zapier“Find relevant people at a company or lookalike companies”

Runs a prospector agent to find relevant people inside a company, or companies that look like it. A switch asks for a lighter version of the contact data.

When to use it
a deal is won and you want lookalike accounts listed for the next outbound push.
Watch out
the minimal response returns fewer fields, so check that the ones you map still exist.
12

Run Sequence

Action

In Zapier“Generate emails for a person using a sequence agent”

Has a sequence agent draft the emails of an outreach sequence for one person. Experiments appear in the agent list as well.

When to use it
a contact qualifies, and the drafted emails should land in your sending tool for a rep to review.
Watch out
the action writes the emails, it does not send them: a later step has to.
13

Update Agent

Action

In Zapier“Update an existing agent configuration”

Changes the setup of an agent that already exists, found by its OId.

When to use it
the product team edits the positioning in a shared doc and the matching agent should be adjusted without someone opening Octave.
Watch out
without the right OId the action has nothing to edit, so keep it in a column or fetch it with a search step first.
14

Run Agent Asynchronously

Action

In Zapier“Triggers an agent to run in the background. Results will be sent to your callback URL when complete. No timeout limits.”

Starts an agent in the background with no time limit. Octave posts the result to a callback address you provide once the job is done.

When to use it
heavy research runs that would be too slow for a step that waits for its answer.
Watch out
the callback URL is mandatory, so you need a second Zap or a tool ready to catch the result.
15

Get Async Agent Run Status

Action

In Zapier“Check the status of a previously started async agent run by request ID”

Reads where a background agent run stands, from the request ID that Run Agent Asynchronously handed back.

When to use it
a later Zap needs to know whether the research is finished before writing anything to the CRM.
Watch out
keep the request ID somewhere a later step can reach, otherwise there is nothing to check.
16

Apply Brand Voice

Action

In Zapier“Apply a brand voice to source materials (rewrites in the voice)”

Rewrites your source material in a brand voice. Sources can be plain text, links or Octave resources, and the original can be returned alongside.

When to use it
partner-written copy arrives through a form and must sound like your company before publishing.
Watch out
sources go in as a structured list, so a raw paragraph pasted in the field is rejected.
17

Create Brand Voice

Action

In Zapier“Create a new brand voice”

Saves a fresh brand voice from a title and a description you write yourself.

When to use it
an agency onboards a client and wants that client's tone stored in Octave as soon as the brief is approved.
Watch out
nothing is generated here: the voice is exactly as good as the description you map into it.
18

Generate Brand Voice

Action

In Zapier“Generate a brand voice from source materials using AI”

Lets Octave's AI deduce a brand voice from material you give it: texts, URLs or existing resources, under a name you choose.

When to use it
a new sub-brand launches its website, and its voice should be derived from those pages instead of written by hand.
Watch out
sources must follow the structured list format, not loose text.
19

Toggle Default Brand Voice

Action

In Zapier“Toggle a brand voice as the workspace default”

Switches which brand voice the workspace uses by default, from the OId of the voice.

When to use it
a seasonal campaign starts and every generated message should pick up its tone without each agent being edited.
Watch out
the OId must point to the voice you want as default, so take it from List Brand Voices rather than typing it.
20

Update Brand Voice

Action

In Zapier“Update an existing brand voice”

Edits a brand voice already stored in Octave, located through its OId.

When to use it
marketing approves a new tone guide in a doc tool and the stored voice should follow.
Watch out
every agent that relies on this voice writes differently from the next run on, so warn the reps.
21

Create Buying Trigger

Action

In Zapier“Create a new buying trigger”

Adds a buying trigger, the kind of event that signals an account may be ready to buy, starting from just a name.

When to use it
sales leadership logs a new signal in a shared form and it should be available to every agent.
Watch out
do not confuse it with a Zapier trigger: this one lives inside Octave and starts nothing.
22

Delete Buying Trigger

Action

In Zapier“Delete a buying trigger by OId”

Removes a buying trigger from Octave by its OId.

When to use it
a quarterly review marks a signal as obsolete in your planning sheet, and the cleanup in Octave should follow on its own without a manual pass.
Watch out
filter carefully on the rows that should really go, the action does not ask for confirmation.
23

Generate Buying Triggers

Action

In Zapier“Generate buying triggers from source materials using AI”

Produces buying triggers with AI from texts, links or resources, one entry per item you send, with an optional name each.

When to use it
a market study lands in your drive and its signals should become usable buying triggers.
Watch out
the input is a structured list, so build it carefully in the mapping.
24

Update Buying Trigger

Action

In Zapier“Update an existing buying trigger”

Changes an existing buying trigger, pointed at by its OId.

When to use it
the definition of a signal gets refined after a few lost deals and the sales ops sheet is the place where people edit it.
Watch out
the OId is required, so the sheet needs a column holding it for every signal.
25

Create Competitor

Action

In Zapier“Creates a new competitor”

Adds a competitor to Octave with nothing more than its name, so agents can position against it.

When to use it
a rep notes a new rival in a deal and the name should reach Octave without a ticket to ops.
Watch out
nothing stops duplicates, so search with Find Competitor or List Competitors first.
26

Delete Competitor

Action

In Zapier“Deletes a competitor by OId”

Takes a competitor out of Octave through its OId.

When to use it
a rival gets acquired or leaves your market, and the competitive file in your wiki is archived, so Octave should drop it too.
Watch out
a wrong OId removes another rival, so take it from Find Competitor or List Competitors.
27

Generate Competitor

Action

In Zapier“Generate competitors from source materials using AI”

Builds competitor profiles with AI from text or URLs, one profile per entry in the list you pass.

When to use it
product marketing drops a batch of rival websites in a sheet and each should become a documented competitor.
Watch out
the list format is strict, and each entry turns into a separate profile.
28

Update Competitor

Action

In Zapier“Updates an existing competitor”

Edits a competitor record already in Octave, using its OId.

When to use it
your battlecard tool changes a rival's positioning after a launch, and Octave should carry the same version to the agents.
Watch out
map the OId from a search step if your source does not store it.
29

Create Experiment

Action

In Zapier“Creates a new agent experiment for A/B testing”

Sets up an A/B test between agents: you give it a name, an agent type, a run strategy and the OIds of the agents to compare, separated by commas.

When to use it
a growth team wants to test two sequence agents on the same audience.
Watch out
all the agents listed should share the type you declare.
30

Create Persona

Action

In Zapier“Creates a new persona”

Records a new persona, the profile of a person you sell to, from a name.

When to use it
a new buyer role keeps showing up in won deals and should exist in Octave for qualification.
Watch out
a persona with only a name gives qualification agents little to work with, so enrich it later.
31

Delete Persona

Action

In Zapier“Deletes a persona by OId”

Deletes a persona in Octave from its OId.

When to use it
a segment is dropped from your strategy, its row is flagged as retired in the planning sheet, and the matching persona should go with it.
Watch out
Qualify Person stops matching against it straight away.
32

Generate Persona

Action

In Zapier“Generate personas from source materials using AI”

Has the AI draft personas from your material, texts or links, one persona per entry of the list.

When to use it
customer interviews are transcribed into a doc and each transcript should yield a persona.
Watch out
the structured list is required, plain text in the field fails.
33

Update Persona

Action

In Zapier“Updates an existing persona”

Edits an existing persona, found by its OId.

When to use it
research confirms a new pain point for a buyer role, the research team logs it in a database, and Octave should reflect it before the next campaign.
Watch out
qualification results change for everyone matched against this persona.
34

Create Playbook

Action

In Zapier“Creates a new playbook”

Adds a playbook attached to a product: you supply the product OId, a description and a key insight, and can ask for templates to be created.

When to use it
a product launch is approved and the sales motion around it should exist in Octave on day one.
Watch out
the product must exist first, since its OId is required.
35

Delete Playbook

Action

In Zapier“Deletes a playbook by OId”

Removes a playbook from Octave by OId.

When to use it
an offer is retired in your catalog tool and the playbook built around it should be cleaned up at the same time, before reps keep relying on it.
Watch out
check that no agent still depends on it.
36

Update Playbook

Action

In Zapier“Updates an existing playbook”

Changes a playbook that already exists, from its OId.

When to use it
enablement reworks the key insight after a win-loss review, logs it in its tracker, and the stored playbook should carry the new angle.
Watch out
keep the playbook OIds in your tracker, or fetch them with Find Playbook first.
37

Create Product

Action

In Zapier“Creates a new product”

Registers a new product in Octave from its name.

When to use it
a new SKU is added to your billing or catalog tool and sales agents should know it exists.
Watch out
the name alone is a thin description, so qualification on this product stays rough until someone details it.
38

Delete Product

Action

In Zapier“Deletes a product by OId”

Removes a product through its OId.

When to use it
a product is discontinued in your catalog and should stop appearing in qualification verdicts and generated messages from the next run on.
Watch out
playbooks attached to that product lose their anchor.
39

Generate Product

Action

In Zapier“Generate a product from source materials using AI”

Lets the AI write product records from texts or URLs, with an optional name for each request in the list.

When to use it
a product page goes live and Octave should learn the offer from it instead of a manual entry.
Watch out
the requests must follow the structured list format.
40

Update Product

Action

In Zapier“Updates an existing product”

Edits a product already known to Octave, using the OId of that product.

When to use it
pricing or packaging changes in your catalog and the description agents rely on should match.
Watch out
a wrong OId edits the wrong product, so take it from Find Product rather than typing it.
41

Create ProofPoint

Action

In Zapier“Creates a new proofPoint”

Stores a proof point, a fact that backs up your pitch, with a name and a type.

When to use it
customer success logs a measurable win and agents should be able to quote it in messages.
Watch out
the type is required, pick it in the dropdown rather than mapping free text.
42

Generate ProofPoint

Action

In Zapier“Generate proofPoints from source materials using AI”

Extracts proof points with AI from your sources, texts or URLs, one per entry in the list.

When to use it
a new case study is published and its arguments should become reusable proof points.
Watch out
review what comes out before agents use it in outbound emails.
43

Update ProofPoint

Action

In Zapier“Updates an existing proofPoint”

Changes a proof point already stored, located by its OId.

When to use it
a figure behind a proof point gets refreshed in the reporting tool after a new quarter and the stored version should not drift.
Watch out
this action and Delete Proof Point use two different spellings in the editor, so search both.
44

Delete Proof Point

Action

In Zapier“Deletes a proof point by OId”

Erases a proof point from Octave, given its OId.

When to use it
a customer withdraws permission to be cited, the account flag changes in your CRM, and the related proof should go at once.
Watch out
sequences generated before the deletion still contain it.
45

Create Reference

Action

In Zapier“Create a new customer reference”

Adds a customer reference under an external-facing name, such as a description of the customer rather than its brand.

When to use it
a deal closes and the account agrees to serve as an anonymous reference.
Watch out
the name is what prospects read, so avoid internal code names.
46

Delete Reference

Action

In Zapier“Deletes a reference by OId”

Removes a reference through its OId.

When to use it
a referenced customer churns in your billing tool, and agents should stop citing that account in the emails they draft from the next run on.
Watch out
a wrong OId removes the wrong reference, so take it from Find Reference.
47

Generate References

Action

In Zapier“Generate customer references from source materials using AI. Each input generates one reference. Supports text, URLs, and generative names as sources.”

Creates customer references with AI. Each entry of the list yields one reference, from text, links or a generated name.

When to use it
win notes accumulate in your CRM and each should become a usable reference.
Watch out
one input equals one reference, so a long list creates many records at once.
48

Update Reference

Action

In Zapier“Updates an existing customer reference”

Refreshes a customer reference already on file, from its OId.

When to use it
the customer expands its contract, the account record changes, and the story agents tell about it should be updated as well.
Watch out
fetch the OId with Find Reference when your CRM does not keep it.
49

Create Resource

Action

In Zapier“Create a resource in your knowledge base (text, file, URL, or Google Drive)”

Puts a document into the Octave knowledge base. A mode field picks the source: text, file, URL or Google Drive.

When to use it
a new sales deck is saved in a shared folder and agents should read it from then on.
Watch out
URL and Drive resources are processed in the background, so they are not usable at once.
50

Delete Resource(s)

Action

In Zapier“Delete one or more resources by OId (comma-separated for bulk)”

Deletes one resource, or several at once when you separate the OIds with commas.

When to use it
a batch of outdated documents is flagged in a sheet and should leave the knowledge base together.
Watch out
a stray comma in the mapped value can remove a resource you meant to keep.
52

Get Resource Status

Action

In Zapier“Check processing status of an async resource (URL or Drive mode)”

Tells where processing stands for a resource added in URL or Drive mode, from its OId.

When to use it
a Zap adds a long document and a later step should run only once Octave has finished reading it.
Watch out
the status is a snapshot at that moment, it does not wait for the end.
53

Create Segment

Action

In Zapier“Creates a new segment”

Defines a new segment, a group of accounts you target, starting from a name.

When to use it
marketing opens a new vertical and qualification should take it into account from the first lead.
Watch out
a segment with only a name gives Qualify Company very little to judge on.
54

Delete Segment

Action

In Zapier“Deletes a segment by OId”

Removes a segment from Octave using its OId.

When to use it
a market is abandoned after a strategy review, the plan is updated in your planning tool, and accounts should no longer qualify for it.
Watch out
verdicts already written in your CRM do not change retroactively.
55

Generate Segment

Action

In Zapier“Generate segments from source materials using AI”

Asks the AI to describe segments from your sources, one segment per entry of the structured list.

When to use it
an analyst shares a report on a new market and each target group in it should become a segment.
Watch out
check the generated descriptions before they drive qualification.
56

Update Segment

Action

In Zapier“Updates an existing segment”

Adjusts an existing segment through its OId.

When to use it
the ideal account size of a vertical shifts after a pricing change, the targeting sheet is edited, and the segment should follow.
Watch out
qualification on that segment changes for every account checked afterwards.
57

Create Solution

Action

In Zapier“Create a new solution”

Creates a solution from a name and a list of sources, which can be text, links, resources, OIds or company names. You can also mark it active and turn on RAG enrichment (retrieval from your knowledge base).

When to use it
presales packages a new offer for one industry.
Watch out
sources must be a structured list.
58

Delete Solution

Action

In Zapier“Delete a solution by OId”

Erases a solution from Octave by its OId.

When to use it
an offer is withdrawn in your catalog tool and should disappear from what agents propose to prospects in their next generated messages.
Watch out
a wrong OId erases another offer, so take it from Find Solution or List Solutions.
59

Generate Solution

Action

In Zapier“Generate a solution from source materials using AI”

Has Octave's AI assemble a solution from a name and source material, with optional RAG enrichment to draw on your knowledge base.

When to use it
a solution brief is written in a doc and Octave should turn it into a structured record.
Watch out
sources accept text, URLs and resources only, fewer types than Create Solution.
60

Update Solution

Action

In Zapier“Update an existing solution”

Rewrites a solution from its OId and a full data block covering the name, internal name, description and qualifying questions.

When to use it
an offer gets reworked end to end and a single step should push the new version.
Watch out
the data field replaces the whole record, so send every part, not only the changed one.
61

Create UseCase

Action

In Zapier“Creates a new useCase”

Adds a use case, a concrete situation where your product helps, starting from a name.

When to use it
a rep spots a new way customers use the product and logs it in a form for marketing.
Watch out
one name gives agents a thin picture, so fill in the details in Octave afterwards.
62

Generate UseCase

Action

In Zapier“Generate useCases from source materials using AI”

Drafts use cases with AI from texts or URLs, one per entry of the list.

When to use it
a feature page or a customer story is published and the situations it describes should feed your messaging.
Watch out
a list of many entries creates many use cases in a single run.
63

Update UseCase

Action

In Zapier“Updates an existing useCase”

Brings an existing use case up to date, located by its OId.

When to use it
product ships an improvement that changes how a use case plays out, the release note is filed, and Octave should carry the new version.
Watch out
the spelling differs from Delete Use Case in the editor, look for both.
64

Delete Use Case

Action

In Zapier“Deletes a use case by OId”

Deletes a use case from Octave given its OId.

When to use it
a feature is sunset in your roadmap tool and the use case built on it should stop showing up in generated messaging from then on.
Watch out
map the OId from Find Use Case rather than typing it by hand.
65

Run Workflow

Action

In Zapier“Trigger an Octave workflow asynchronously. Returns a job OId you can poll with Get Workflow Run Status.”

Starts one of your Octave workflows in the background and returns a job OId right away, not the final result.

When to use it
a multi-stage Octave process should kick off when a deal reaches a given stage in your CRM.
Watch out
store the job OId, it is the only way to read the outcome later.
66

Get Workflow Run Status

Action

In Zapier“Get the current status of a workflow run by job OId. Poll every 5-10 seconds.”

Checks how a workflow run is going, from the job OId that Run Workflow returned.

When to use it
a follow-up Zap reads the status before copying the workflow output to your CRM.
Watch out
Octave suggests checking every 5 to 10 seconds, and each successful check counts a task.
Searches

The 26 Octave searches

26 search steps look for data that already exists in Octave, so a later step can use it.

In the editor, the searches sit at the bottom of the action list under their own SEARCH heading. Some action fields also offer + Add search step, which inserts the lookup just before and wires its result in. Octave searches mostly work on OIds, so they are how a Zap fetches an identifier no earlier step carried. Octave exposes no find-or-create variant.

1

List Agents

Search

In Zapier“List all agents with optional filtering”

Returns the agents of your workspace, with optional filtering, either all of them or up to a limit.

When to use it
a weekly report Zap needs an inventory of agents to post in a team channel.
Watch out
turn on Return All when you want the full list, otherwise you only get part of it.
2

Find Agent

Search

In Zapier“Finds a specific agent by OId”

Fetches one agent from its OId and hands its details to the following steps.

When to use it
before Update Agent, to read the current setup and decide whether the change is still needed.
Watch out
it only looks up by OId, not by name, so the identifier has to come from somewhere upstream.
3

Find Brand Voice

Search

In Zapier“Finds a specific brand voice by OId”

Retrieves a single brand voice when you give it the OId.

When to use it
a content Zap wants to display the voice description next to the drafted text so a reviewer can judge the fit before approving the draft.
Watch out
no OId, no result, and by default the Zap stops there.
4

List Brand Voices

Search

In Zapier“Retrieves a list of brand voices”

Brings back the brand voices stored in Octave, all or a limited batch.

When to use it
an audit Zap copies every voice into a sheet so marketing can review them together.
Watch out
without Return All, voices beyond the limit are left out silently.
5

Find Buying Trigger

Search

In Zapier“Finds a specific buying trigger by OId”

Looks up one buying trigger from its OId.

When to use it
a deal note references a signal and the next step should quote its full definition in the CRM, so reps see exactly what was detected.
Watch out
mind the three settings above if the OId may point to a deleted signal.
6

List Buying Triggers

Search

In Zapier“Retrieves a list of buying triggers”

Returns the buying triggers recorded in your workspace.

When to use it
sales ops wants an up-to-date table of signals in a shared sheet every time a review meeting is scheduled.
Watch out
with several results, the default keeps only the first, so choose to pass them all on when you need the full table.
7

Find Competitor

Search

In Zapier“Finds a specific competitor by its OId”

Fetches the record of one competitor from its OId.

When to use it
a lost deal is logged with a competitor reference, and the next step attaches that rival's profile to the loss report for the review.
Watch out
the field says OID in capitals, but it is the same identifier as elsewhere.
8

List Competitors

Search

In Zapier“Retrieves a list of competitors”

Gives back the competitors stored in Octave, all or a limited number.

When to use it
before Create Competitor, to check the rival is not already there and avoid a duplicate.
Watch out
a list search followed by a create makes the Zap multi-step, so it needs a paid plan.
9

Find Persona

Search

In Zapier“Finds a specific persona by its OId”

Retrieves a persona from its OId so its details can feed later steps.

When to use it
a message template in your outreach tool should include the pains of the persona a contact matched.
Watch out
a stale OId returns nothing, and the default stops the Zap.
10

List Personas

Search

In Zapier“Retrieves a list of personas”

Lists the personas defined in your workspace.

When to use it
a quarterly Zap exports the personas into a doc for the sales kickoff, so the whole team works from the same profiles during the meeting.
Watch out
switch on Return All for the complete set rather than the first batch.
11

Find Playbook

Search

In Zapier“Finds a specific playbook by its OId”

Pulls a single playbook when given its OId.

When to use it
just before Update Playbook, to compare the stored key insight with the new one and update only when they differ.
Watch out
it does not search by product, only by playbook OId.
12

List Playbooks

Search

In Zapier“Retrieves a list of playbooks”

Returns the playbooks stored in Octave, all or a limited set.

When to use it
enablement wants a single sheet summing up every playbook per product, refreshed whenever a new product row is added.
Watch out
many results with the default setting means only the first one travels on.
13

Find Product

Search

In Zapier“Finds a specific product by its OId”

Retrieves the product whose OId you pass, with its description.

When to use it
a quote Zap needs the product wording stored in Octave to stay consistent with what agents say to prospects.
Watch out
it expects the OId of the product, not its name.
14

List Products

Search

In Zapier“Retrieves a list of products”

Collects the products of your workspace, all or up to a limit.

When to use it
a catalog sync Zap compares Octave's products with your billing tool to spot gaps.
Watch out
choose to hand all results on, otherwise the comparison sees one product only.
15

Find ProofPoint

Search

In Zapier“Finds a specific proofPoint by its OId”

Fetches one proof point by its OId.

When to use it
a proposal Zap drops a specific proof into a document template before it reaches the prospect, instead of a rep pasting it in by hand.
Watch out
if the proof was deleted, the search returns nothing and the template step is skipped by default.
16

List ProofPoints

Search

In Zapier“Retrieves a list of proofPoints”

Lists the proof points stored in Octave.

When to use it
marketing reviews every proof each quarter in a sheet and checks which ones still hold, before the next round of campaigns starts.
Watch out
without Return All, the review sees only part of the proofs.
17

Find Reference

Search

In Zapier“Finds a specific reference by its OId”

Opens one customer reference from its OId.

When to use it
a rep requests a reference through a form and the reply should include the stored description, so the prospect gets a consistent story every time.
Watch out
the external name returned is what the prospect will read.
18

List References

Search

In Zapier“Retrieves a list of references”

Returns the customer references kept in your workspace.

When to use it
a monthly digest lists the available references for the sales team in a chat channel, so reps know which stories they can use.
Watch out
the default keeps the first match only when several come back, change it for a digest.
19

Find Resource

Search

In Zapier“Finds a specific resource by OId”

Fetches one knowledge-base resource from its OId, and can also report on its storage task.

When to use it
a Zap that added a Drive file checks whether Octave has finished storing it.
Watch out
the storage check is a separate option, set it when the status is what you need.
20

List Resources

Search

In Zapier“Retrieves a list of knowledge-base resources”

Lists the resources of your knowledge base, all or a limited batch.

When to use it
an ops Zap mirrors the list into a sheet to spot outdated documents worth removing, then feeds those rows to the deletion step.
Watch out
turn on Return All, otherwise the sheet only gets the first batch.
21

Find Segment

Search

In Zapier“Finds a specific segment by its OId”

Fetches the segment matching an OId.

When to use it
after Qualify Company, to write the full segment name next to the verdict in your CRM, so reps understand why an account was routed to them.
Watch out
the field is labeled OID, the value is the usual Octave identifier.
22

List Segments

Search

In Zapier“Retrieves a list of segments”

Returns the segments defined in your workspace.

When to use it
a planning Zap pulls every segment into a board each time a new quarter column is created.
Watch out
pass all results on, otherwise only one segment lands in the board.
23

Find Solution

Search

In Zapier“Finds a specific solution by OId”

Retrieves the solution matching the OId you pass.

When to use it
before Update Solution, to read the full record, since the update replaces everything at once.
Watch out
map the fields you read here into the update, or the parts you skip are lost.
24

List Solutions

Search

In Zapier“Retrieves a list of solutions”

Lists solutions, with an option to keep only the active ones.

When to use it
a proposal tool should only offer solutions currently live in Octave, never the archived ones.
Watch out
Active Only and Return All are two separate switches, set both.
25

Find Use Case

Search

In Zapier“Finds a specific use case by its OId”

Fetches a single use case when given its OId.

When to use it
a customer story form references a use case and the next step should pull its wording, so the published story stays aligned with what agents say.
Watch out
a deleted use case returns nothing and stops the Zap by default.
26

List UseCases

Search

In Zapier“Retrieves a list of useCases”

Returns the use cases recorded in Octave, all or a limited number.

When to use it
product marketing exports them into a wiki page to keep messaging aligned across teams and regions.
Watch out
the default keeps the first result only, switch it to pass them all.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create. Octave offers no such variant, so this box does not appear on its searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When an Octave Zap breaks

Zapier attaches no help article to Octave, so the traps below are the ones every Zap shares, read through Octave's actions.

Most of the traps below start in the trigger app or come from a missing identifier. The Zapier troubleshooting page walks through the general diagnosis.

  • The backlog is never picked up

    A Zap only reacts to what happens after it is switched on. Accounts already sitting in your sheet or CRM are not enriched, moving them is a separate job.

  • A loop that eats your tasks

    If the Zap writes Octave's answer back into the sheet its own trigger watches, it can set itself off again and again and burn through the task count fast.

  • A bulk import gets held back

    After a mass import, the starting app can return a huge batch at once, and Zapier's flood protection may hold it back instead of sending everything to Octave.

  • No duplicate runs on polling

    On a polling trigger, Zapier remembers what it has already seen, so the same row does not start the Zap twice. Each row starts it once, never twice.
Need help

Need help automating Octave with Zapier?

A person reads every message.

FAQ

Octave Zapier integration: frequent questions

01Is the Octave Zapier integration free?
Yes, on the Zapier side. Octave is not a premium app, so it works from the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the step limit: a free Zap holds one trigger and one action only. Since Octave has no trigger, the free Zap is another app starting it plus one Octave action. Enriching then qualifying, or adding a filter or a search step, makes the Zap multi-step, and that requires a paid plan. The Octave subscription itself is a separate matter not covered here.
02How many tasks does an Octave Zap use?
One task per Octave action that completes successfully, and nothing for the trigger. A Zap that runs Enrich Company then Qualify Company costs two tasks each time a new row arrives. An action that fails is not counted. Checking the starting app for new data is free too, however often Zapier looks. Watch the status checks: Get Workflow Run Status and Get Async Agent Run Status are actions, so each successful check counts one task, and checking often on many runs adds up quickly.
03Does Octave work in real time with Zapier?
Octave cannot start a Zap, because it exposes no trigger. The Zap starts in another app, and its speed depends on that app. If that trigger is instant, the app reports the event to Zapier straight away. If it is a polling trigger, Zapier checks it at your plan's interval: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Once started, the Octave action runs as the next step. Long jobs such as Run Workflow answer later, through a status check.
04What do you need to connect Octave to Zapier?
An Octave account, and access to whatever the Zap should touch. In Zapier, open Apps, click + Add connection, pick Octave and click Add connection, then sign in to Octave in the tab that opens and grant access. Before building the Zap, make sure the agents it calls exist in your workspace: most actions ask for a specific agent, such as an enrich company agent or a sequence agent, and the dropdown only lists those already created.
05Why does Run Agent Asynchronously need a callback URL?
Because the answer does not come back in the Zap. The action starts the agent in the background, with no time limit, and Octave sends the result to the address you provide once the job is done. The field is mandatory, so another Zap or a tool must be ready to receive that result. If you only need to know whether the run is finished, Get Async Agent Run Status reads its state from the request ID returned at launch.
06What if the Octave operation you need is not listed?
Check both lists first: some lookups, such as Search Resources, sit among the actions rather than under the searches heading. If nothing matches, the usual way around is to combine existing steps, for example a List search followed by an Update action. Octave also offers Run Workflow, which starts a full Octave workflow from a single Zap step, so a sequence built inside Octave can cover what no single action does. Nothing on the Zapier side can add an operation the app does not expose.
07Zapier, Make or n8n for Octave?
It depends on your criteria rather than on a winner. Zapier offers 66 actions and 26 searches for Octave, with no trigger, and a free plan capped at two steps. Make has its own Octave app, worth comparing operation by operation if you need branching scenarios. n8n has its own logic and pricing, to check on its side. Compare the operations you actually need, the volume of runs, and who will maintain the automation over time.
Same platform

Other docs you might need on this stack.

Browse all integrations