Resources · Make integration

Octave Make integrationAutomate Octave with Make.

Can Make run your Octave agents for you? Yes. The Octave Make integration gives you 101 modules, 83 actions and 18 searches, for sales and marketing teams who want Octave fed by their other apps. This page shows how to connect it and build a first scenario.

Try the Octave integration on Make See the 101 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Octave Make integration do for you?

The Octave Make integration links your Octave workspace to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, here an Octave action or search, so Octave can run its agents and update its records when something happens in another app.

Enriched accounts without copy and paste. A new company appears in your CRM, and Run an enrich company agent starts on it. The bundle Octave returns (a bundle is one item passed from a module to the next) can then flow into the next app of the chain.

Leads sorted before a rep calls. Run a qualify person agent or Run a qualify company agent takes over when a form comes in, and Run a call prep agent covers the step right before a meeting.

A library that stays current. Personas, competitors, products and proof points each have a Create, Update and Delete module, so a spreadsheet your team already maintains can keep Octave in line.

Two limits matter. Octave has no trigger module, so the scenario starts from another app or from a schedule. And the Octave documentation in Make is AI-generated content that may contain mistakes, so test each module with Run once. The Make training covers the editor basics, Make troubleshooting helps when a run fails, and n8n vs Make compares both tools if you hesitate.

Connect

How do you connect Octave to Make?

01
Generate your API key in Octave
You need an active Octave account. In Octave, open the Developers tab in the top menu, click the button that generates a new API key for your workspace, then copy the key shown on screen.
02
Add an Octave module in Make
In your scenario, add any Octave module and click Create a connection. A connection is your Octave account linked to Make once and reused by every Octave module. The Connection name field is optional but helps later.
03
Paste the key and save
Paste the API key you copied from Octave, or follow the instructions Make displays, and confirm. Make can now list what your workspace holds when you fill the next module fields.

First scenario

Your first scenario with Octave

GoalWhen a new company lands in your CRM, Make runs Octave's enrich company agent on it.

01
Create the scenario
From the Scenarios page, create a new scenario and click the + to place the first module. Octave has no trigger, so this first spot goes to your CRM or form app.
02
Set the starting module
Pick the module of that other app that watches for new companies, and create its connection. Make then lists the objects it can read so you choose the right one.
03
Add the Octave agent
Click the + on the right, search for Octave, pick Run an enrich company agent and create your Octave connection with the API key. Map the company data from the first module.
04
Test with Run once
Click Run once. Make runs the scenario one time; then read the bundles each module received, including the one Octave sent back.
05
Schedule and switch it on
Open the clock on the first module. The default schedule of a new scenario is every 15 minutes; adjust it within your plan's limits, then switch the scenario on.

Modules

What the Octave modules do

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

Octave1

Apply a brand voice

ActionIn the docs only

Apply a brand voice puts one of the voices saved in your Octave workspace to work inside a scenario, so the text your flow carries follows the tone your team agreed on.

When to use it

right before a module that sends copy to another app, such as an email draft or a CRM note.

Watch out

click Run once and read the bundle it returns before letting the scenario run on real contacts.

Octave2

Build a workspace

ActionIn the docs only

Build a workspace starts an Octave workspace from Make rather than from the Octave screens, so a new space can appear as soon as an event in another app calls for it.

When to use it

when each new client or business unit gets its own workspace, and a signed deal in your CRM is the signal.

Watch out

Octave generates API keys per workspace, so check which connection the next modules in the scenario use.

Octave3

Create a brand voice

ActionIn the docs only

With Create a brand voice, a new voice lands in Octave from data your scenario already holds, like a style guide stored in a document or the answers of an internal form.

When to use it

when marketing validates a tone and wants Octave to hold it without anyone retyping it.

Watch out

every Run once adds one more voice, so delete the test copies once the scenario works.

Octave4

Create a buying trigger

ActionIn the docs only

A buying trigger saved in Octave is only one module away: Create a buying trigger records a new one from the bundle your scenario carries, without a trip through the Octave interface.

When to use it

when sales spots a signal worth tracking, logged as a row in a shared sheet, and wants it stored in Octave too.

Watch out

despite its name, this is an action module; it cannot start a scenario the way a trigger does.

Octave5

Create a competitor

ActionIn the docs only

Create a competitor adds a rival to your Octave records straight from Make, using the values you map from the previous module.

When to use it

a sales rep types a new competitor name in a CRM field, and Octave should know about it without a second entry.

Watch out

run List competitors first if the same rival might already exist, or you will end up with two entries for one company.

Octave6

Create a persona

ActionIn the docs only

Adding a buyer profile to Octave no longer requires the Octave screens: Create a persona writes it from the fields mapped in your scenario.

When to use it

after a positioning workshop whose notes sit in a spreadsheet, each row becoming one persona in Octave.

Watch out

one row is one bundle and one operation (a single module run, what Make counts on your plan), so a long sheet consumes many.

Octave7

Create a playbook

ActionIn the docs only

Create a playbook stores a new playbook in Octave from your scenario, taking its content from whatever the earlier modules provide.

When to use it

a new offer launches and the sales approach written in a shared document has to exist in Octave as well.

Watch out

a playbook created while testing stays in the workspace; remove it with Delete a playbook if the run was only a trial.

Octave8

Create a product

ActionIn the docs only

Your catalog changes in one tool and Octave follows: Create a product records a new product each time the scenario receives one.

When to use it

a product added to your back office or product sheet should also exist in Octave for your agents.

Watch out

test on a single row with Run once before letting a full import through, since each bundle creates one product.

Octave9

Create a proof point

ActionIn the docs only

Create a proof point saves a new proof point in Octave from the data your scenario passes along, so evidence approved elsewhere is ready for your sales team.

When to use it

a client approves a result and your team logs it in the CRM or in a form.

Watch out

place this module after the approval step of your flow, never before, so only validated evidence reaches Octave.

Octave10

Create a reference

ActionIn the docs only

Create a reference adds a new reference to Octave from the values mapped in the module, so your list of references grows as deals move.

When to use it

a deal closes and the client agrees to be cited, which your CRM records as a status change.

Watch out

the scenario copies what it receives; check the client's agreement upstream, in the app that starts the flow.

Octave11

Create a resource

ActionIn the docs only

Create a resource hands a new resource to Octave from Make, so material your team publishes elsewhere is also available on the Octave side.

When to use it

a document or page is published in another tool and Octave should get it too.

Watch out

pair it with Get a resource status, which tells you where the new resource stands before a later module relies on it.

Octave12

Create a segment

ActionIn the docs only

A new market segment can reach Octave without manual entry: Create a segment writes one from the data mapped in the module.

When to use it

marketing opens a new target, for example a vertical added to a planning sheet, and knows exactly how to define it.

Watch out

Generate segments exists too; choose Create when you already know the segment, Generate when you want Octave to propose some.

Octave13

Create a service

ActionIn the docs only

Create a service records a service in Octave, the counterpart of Create a product for what you sell as work rather than as goods.

When to use it

an agency adds a new offer to the catalog it keeps in a sheet, and Octave should list it right away.

Watch out

Octave keeps products, services and solutions apart, so pick the module that matches how your workspace is organized.

Octave14

Create a solution

ActionIn the docs only

Create a solution adds a solution to Octave straight from your scenario, filled with the values you map from earlier modules.

When to use it

a new offer is written up in another tool first, and the Octave side should match it without retyping.

Watch out

Generate a solution is the other route, when you would rather let Octave draft the solution than supply every value yourself.

Octave15

Create a use case

ActionIn the docs only

Create a use case saves a new use case in Octave from the data of your scenario, so stories collected by other teams do not stay in their tools.

When to use it

your product team logs a new usage story in a form or a ticket, and sales should find it in Octave.

Watch out

if the same story can come from two sources, filter duplicates in Make before this module.

Octave16

Create an agent

ActionIn the docs only

Create an agent sets up a new Octave agent from Make rather than from the Octave interface, so agents can be created as part of a larger flow.

When to use it

every new workspace needs the same agent, so a scenario builds it right after Build a workspace.

Watch out

List agent types shows which types exist; map one of its values instead of typing a type by hand.

Octave17

Create an agent experiment

ActionIn the docs only

Create an agent experiment starts an experiment on an Octave agent from your scenario, which keeps the setup of each test traceable in Make.

When to use it

you want to try a variant of an agent and record, in the same flow, when and why the test began.

Watch out

run it on a test agent first with Run once, then check the experiment in Octave before touching an agent your team relies on.

Octave18

Delete a buying trigger

ActionIn the docs only

Delete a buying trigger removes a buying trigger from Octave once it no longer reflects a real signal in your market.

When to use it

a signal gets marked obsolete in your tracking sheet and Octave should drop it at the same moment.

Watch out

a deletion cannot be undone from Make; map the ID from Get a buying trigger or List buying triggers, never a guessed value.

Octave19

Delete a competitor

ActionIn the docs only

Once a rival leaves your market, Delete a competitor clears it from Octave so your records match what sales actually faces.

When to use it

a merger or a market exit, logged in your CRM, ends the competition with that company.

Watch out

add a filter before the module so only the competitor you meant goes through; nothing brings it back afterwards.

Octave20

Delete a persona

ActionIn the docs only

Delete a persona takes a buyer profile out of your Octave workspace, which keeps the list of personas limited to the ones you still target.

When to use it

a repositioning removes a profile from the target list your team maintains in a sheet.

Watch out

run List personas with Run once first and read the bundles, because deleting the wrong profile has no undo button.

Octave21

Delete a playbook

ActionIn the docs only

Retiring an old sales approach is the job of Delete a playbook, which removes it from Octave for good.

When to use it

an offer is discontinued and its playbook should disappear from Octave at the same moment.

Watch out

if the text might be useful later, add Get a playbook just before and store its content in another app.

Octave22

Delete a product

ActionIn the docs only

Delete a product removes a product from Octave, so the products your agents see stay in line with what you still sell.

When to use it

a product archived in your back office should vanish from Octave too, keeping both lists identical.

Watch out

when a scenario feeds many archived items at once, each bundle deletes one product; test the filter on a single item first.

Octave23

Delete a proof point

ActionIn the docs only

Delete a proof point pulls a piece of evidence out of Octave, which matters when a claim should no longer appear in sales material.

When to use it

a client withdraws permission to be quoted, or a figure your team used goes out of date.

Watch out

the removal is final; log the deleted item in a sheet within the same scenario if your team needs a trail.

Octave24

Delete a reference

ActionIn the docs only

Delete a reference removes a reference from Octave, so a client who stopped working with you is no longer offered as an example.

When to use it

a client relationship ends and its name should no longer be cited by your team.

Watch out

make sure the ID comes from Get a reference or List references; a wrong mapping deletes someone else's reference.

Octave25

Delete a resource

ActionIn the docs only

Delete a resource takes a resource out of Octave, which keeps retired material from lingering next to the current version.

When to use it

a document is withdrawn in your source tool and should not stay available on the Octave side.

Watch out

Search resources helps you find the right item by its content before you remove it, instead of guessing an ID.

Octave26

Delete a segment

ActionIn the docs only

Delete a segment drops a segment from your Octave workspace once your team stops targeting it.

When to use it

marketing closes a target and removes its row from the planning sheet that feeds the scenario.

Watch out

Make cannot restore a deleted segment; put a filter in front so an empty ID never reaches this module.

Octave27

Delete a service

ActionIn the docs only

Delete a service removes a service from Octave when you stop offering that work, so it no longer shows up next to your live offers.

When to use it

an agency drops an offer and updates its own catalog first, and Octave should follow.

Watch out

services, products and solutions each have their own delete module; check that you picked the one matching the item.

Octave28

Delete a solution

ActionIn the docs only

Delete a solution clears an outdated solution from Octave, leaving only the offers your team still presents.

When to use it

a packaged offer is withdrawn and the tool where you document offers marks it as closed.

Watch out

test with Run once on a solution created only for the test, never on a live one.

Octave29

Delete a use case

ActionIn the docs only

Delete a use case removes a use case from Octave when that usage story no longer applies to your offer.

When to use it

a product change makes an old use case wrong, and your team flags it in a ticket or a sheet.

Watch out

List use cases returns several bundles; delete one at a time through a filter rather than every result it finds.

Octave30

Delete an agent

ActionIn the docs only

Delete an agent removes an Octave agent, which is the clean way to retire agents built for a test or for a team that no longer exists.

When to use it

a test agent has served its purpose, or a team is closed in your HR or project tool.

Watch out

any scenario that still runs this agent will point at nothing afterwards; check your other scenarios before deleting.

Octave31

Generate a brand voice

ActionIn the docs only

Generate a brand voice asks Octave to produce a brand voice for you, instead of writing one field by field with Create a brand voice.

When to use it

a workspace starts empty and you want a first voice your marketing team can review.

Watch out

treat the result as a draft: read it, fix it with Update a brand voice, and only then let Apply a brand voice use it.

Octave32

Generate a solution

ActionIn the docs only

Generate a solution has Octave draft a solution, whereas Create a solution expects you to supply every value yourself.

When to use it

a new offer exists only as a few notes and you want a first structured version in Octave.

Watch out

run it with Run once and read what comes back before any other module sends that solution anywhere.

Octave33

Generate buying triggers

ActionIn the docs only

Generate buying triggers lets Octave propose buying triggers for your workspace rather than you listing them one by one.

When to use it

right after Build a workspace, to give an empty space a starting set of signals.

Watch out

if the module returns several items, each one becomes a separate bundle and costs an operation in every module that follows.

Octave34

Generate competitors

ActionIn the docs only

Generate competitors asks Octave for competitors instead of a single rival you already know, a quick way to fill a list that is still empty.

When to use it

your team enters a new market and has not yet mapped who else sells there.

Watch out

compare the proposals with List competitors before saving anything, so the same company does not appear twice.

Octave35

Generate personas

ActionIn the docs only

Rather than drafting every buyer profile by hand, Generate personas has Octave propose them for your workspace.

When to use it

a new product line needs profiles, and your team prefers reviewing proposals to starting from a blank page.

Watch out

the proposals are a starting point; sales should confirm them before any agent relies on them for outreach.

Octave36

Generate products

ActionIn the docs only

Generate products gets Octave to propose products for your workspace, useful when the catalog in Octave is still empty.

When to use it

you set up Octave for a new client and want a first product list to correct rather than type.

Watch out

keep Create a product for the items you already know precisely; this module is for proposals you will review.

Octave37

Generate proof points

ActionIn the docs only

Generate proof points asks Octave to propose proof points, so your team has material to review instead of an empty list.

When to use it

a new offer has no evidence recorded yet in Octave and sales wants something to start from.

Watch out

nothing generated should reach a prospect unchecked; keep a review step, then save only the points your team confirms.

Octave38

Generate references

ActionIn the docs only

Generate references has Octave propose references for your workspace, a first batch to sort through rather than a finished list.

When to use it

your reference list in Octave is empty and you want suggestions to validate with account managers.

Watch out

a reference names a real client, so confirm each one with the client's agreement before anyone cites it.

Octave39

Generate segments

ActionIn the docs only

Generate segments lets Octave suggest segments for your workspace, which helps when you have not yet split your market.

When to use it

a new workspace needs a first view of its targets and marketing wants proposals to discuss.

Watch out

read the result with Run once; the Octave documentation in Make is AI-generated and may contain mistakes, so verify key details.

Octave40

Generate services

ActionIn the docs only

Generate services gets Octave to propose the services of your workspace, the counterpart of Generate products for offers you sell as work.

When to use it

an agency sets up Octave and wants a first list of its services to edit rather than write from nothing.

Watch out

the proposals may not match your real offer; remove the extra ones with Delete a service after review.

Octave41

Generate use cases

ActionIn the docs only

Octave drafts use cases for you, so your workspace gets a starting list of the problems your offer solves without typing each one. The drafts land as data the next module can read.

When to use it

right after you add a new product, to seed the use cases your sales team will pitch.

Watch out

Octave's Make documentation gives no description for this module; run it once and read what it returns before you chain anything to it.

Octave42

Get a brand voice

ActionIn the docs only

This action fetches one brand voice from your Octave workspace, so a later module can write in that tone. You pick which voice, and Make passes it along as a single bundle (one item handed to the next module).

When to use it

before a content step, when copy has to match a house style you already saved in Octave.

Watch out

it returns one voice only; to browse all of them, List brand voices is the right brick.

Octave43

Get a buying trigger

ActionIn the docs only

Pull a single buying trigger out of Octave and hand its details to the rest of your scenario (the automation you build in Make). Handy when an email or a CRM note must mention the exact signal.

When to use it

when a prospect shows a signal you already modeled in Octave and a rep needs the reasoning attached.

Watch out

the name is misleading for Make newcomers: this is an Octave record, not a Make trigger, so it never starts a scenario.

Octave44

Get a competitor

ActionIn the docs only

Reads one competitor profile stored in Octave and makes it available to the modules that follow. Your battlecard content can then travel into a CRM note, a chat message or a document.

When to use it

ahead of a sales call where the deal names a rival you have documented.

Watch out

each run of this module costs one operation (what Make counts on your plan), so fetch the profile once per deal, not once per email.

Octave45

Get a persona

ActionIn the docs only

With this module, a scenario loads one buyer persona from Octave: the profile your team wrote about who buys and why. Later steps can map that profile into messages or records.

When to use it

when a new lead matches a known role and the follow-up should speak to that role.

Watch out

if the persona was deleted in Octave, the module has nothing to return; test with Run once after any cleanup in your workspace.

Octave46

Get a playbook

ActionIn the docs only

Fetch one Octave playbook so its guidance can reach the people or tools that need it. A playbook groups how your team sells to a given situation; this brick brings one of them into the flow.

When to use it

when a deal enters a stage and the owner should receive the matching playbook in the tool they already use.

Watch out

it hands over one playbook; to see which ones exist, run List playbooks first.

Octave47

Get a product

ActionIn the docs only

Loads a single product record from Octave. The description your team wrote stays the reference, and Make copies it into whatever comes next: a quote draft, a sheet row, a message.

When to use it

when an inbound request names one of your products and the reply should use the approved wording.

Watch out

it reads, it never edits. Changes go through Update a product, handled in another part of this page.

Octave48

Get a proof point

ActionIn the docs only

Proof points are the facts that back your claims, and this module fetches one of them from Octave for the rest of the scenario to use in an email, a slide or a CRM field.

When to use it

when a rep asks for evidence on one precise objection and you want the stored answer, not a rewrite.

Watch out

Make shows you only what Octave returns; check the bundle in the Run once output before trusting the fields you map.

Octave49

Get a reference

ActionIn the docs only

Pick up one customer reference from Octave and pass it downstream. It keeps your approved reference as the single source when a scenario assembles sales material.

When to use it

when a prospect in a given industry asks who else uses your offer.

Watch out

references usually carry customer names, so route this data only to tools your whole team is allowed to see.

Octave50

Get a resource

ActionIn the docs only

One resource from Octave, delivered as a bundle: that is what this action gives you. The next module can attach it, summarize it or store its details somewhere else.

When to use it

when a scenario needs the content of a resource you already added to Octave.

Watch out

Get a resource status answers a different question (is it ready yet?); ask for the status first if the resource was just created.

Octave51

Get a resource status

ActionIn the docs only

Checks where a resource stands inside Octave, so your scenario can wait for it before using it. The answer comes back as a bundle the next module can read.

When to use it

right after Create a resource, when the next step should only run once the resource is ready in Octave.

Watch out

the doc lists no status values; read them in the Run once output instead of guessing what they mean.

Octave52

Get a segment

ActionIn the docs only

Returns one market segment defined in Octave, with the details your team saved for it. Downstream modules can then tag a lead, pick a sequence or fill a report column from it.

When to use it

when an account has been classified and you want the segment's own description attached to it.

Watch out

a segment fetched here is a snapshot; if someone edits it in Octave later, older records in other tools keep the old text.

Octave53

Get a service

ActionIn the docs only

Services are what you deliver beyond a product, and this module reads one of them from Octave. The content flows to the next brick exactly as stored.

When to use it

when an onboarding or proposal scenario needs the approved description of the service being sold.

Watch out

do not confuse it with Get a product: the two record types live apart in Octave, so pick the one your team actually filled in.

Octave54

Get a solution

ActionIn the docs only

Brings one solution record from Octave into your scenario. Useful when a message has to explain how your offer answers a problem, in the words your team validated.

When to use it

when a discovery call ends and the recap email should describe the matching solution.

Watch out

an empty result usually means the solution was never saved in this workspace; check the connection (your Octave account linked to Make) points at the right one.

Octave55

Get a use case

ActionIn the docs only

This module retrieves a single use case from Octave: one concrete problem your customers solve with you. Map its content into a pitch, a CRM note or a knowledge base page.

When to use it

when a lead describes a need and your reply should quote the closest documented use case.

Watch out

use cases drafted by Generate use cases may need review first; fetching them does not make them correct.

Octave56

Get a workflow run status

ActionIn the docs only

After Octave starts a workflow, this action tells your scenario how that run is going. It lets Make react to the outcome instead of assuming it went well.

When to use it

following Run a workflow, before any step that depends on the workflow's result.

Watch out

the doc says nothing about how long a run takes, so read the status in the Run once output and plan for a run that is not finished yet.

Octave57

Get an agent

ActionIn the docs only

Reads the settings of one Octave agent so you can see or reuse them elsewhere. It is a look-up, not a launch: nothing runs inside Octave when this module executes.

When to use it

when you want to log which agent a scenario relies on, or copy its setup into a report.

Watch out

to actually launch an agent, reach for one of the Run modules instead.

Octave58

Get an async agent run status

ActionIn the docs only

Pairs with Run an agent (async): once an agent has started in the background, this module asks Octave whether the run has finished and what came of it.

When to use it

when an agent takes a while and your scenario must collect the result before moving on.

Watch out

each check is one operation; do not poll in a tight loop, and plan a separate path for runs that are not done yet.

Octave59

List agent types

SearchIn the docs only

Shows the kinds of agents Octave offers, returned as a list. A search module like this one can hand back zero, one or several bundles, and each bundle goes through the next modules separately.

When to use it

while you design a scenario and want to know which agent types your workspace can create.

Watch out

every bundle it returns runs the following modules once, which can multiply your operations fast.

Octave60

List agents

SearchIn the docs only

Gives you every agent set up in your Octave workspace, one bundle per agent. It is the quickest way to see what is available before wiring a Run or Get module.

When to use it

when you audit your workspace or sync the list of agents into a sheet your team reviews.

Watch out

if you only care about one agent, use Get an agent instead, or the rest of the scenario runs for all of them.

Octave61

List brand voices

SearchIn the docs only

Returns the brand voices saved in Octave, one bundle each. Use it when you do not know in advance which voice a step should pick.

When to use it

when a content scenario serves several brands and must choose the voice that matches the request.

Watch out

Toggle default brand voice changes which voice is the default; this module only reads what exists.

Octave62

List buying triggers

SearchIn the docs only

Pulls the buying triggers your team has modeled in Octave as a series of bundles. From there, Make can copy them to a sheet, a CRM or a team channel.

When to use it

when sales ops wants a shared, up-to-date view of every signal the team watches for.

Watch out

remember that these are Octave records: listing them never starts anything in Make on its own.

Octave63

List competitors

SearchIn the docs only

Hands back all competitor profiles stored in Octave. Each one becomes its own bundle, ready to be written somewhere else or checked against a deal.

When to use it

when a deal mentions a company name and you want to see whether it matches a known rival.

Watch out

a search that returns nothing is a valid result, so plan what happens when the list comes back empty.

Octave64

List languages

SearchIn the docs only

Asks Octave which languages it supports and returns them as bundles. It helps you feed a valid choice into modules that write content, instead of typing a value by hand.

When to use it

when a scenario produces messages for several markets and must pick an available language.

Watch out

the doc does not list the languages themselves; run the module to see what your account gets.

Octave65

List personas

SearchIn the docs only

Retrieves every persona in your Octave workspace, one per bundle. It lets a scenario compare each profile with a lead's role.

When to use it

when incoming leads carry a job title and you want to match them against your personas.

Watch out

without an aggregator (a module that regroups bundles), the next steps run once per persona.

Octave66

List playbooks

SearchIn the docs only

Shows all the playbooks your team keeps in Octave. The result arrives as separate bundles you can loop through, store or send to a channel.

When to use it

when a new hire joins the sales team and should receive the full set of playbooks in one go.

Watch out

long lists cost operations downstream; aggregate them into one message before sending.

Octave67

List products

SearchIn the docs only

Returns the product catalog kept in Octave as a set of bundles. That lets Make mirror it into a spreadsheet, a site or another sales tool.

When to use it

when your product records in Octave must stay aligned with the list in your CRM.

Watch out

this only reads; syncing back needs Update a product or Create a product on the Octave side.

Octave68

List proof points

SearchIn the docs only

Collects every proof point from Octave so a scenario can sort, filter or share them. Each proof point travels as its own bundle.

When to use it

when a marketer asks for all evidence available before building a case study page.

Watch out

the doc describes no way to narrow the list, so plan for many bundles, each one costing operations downstream.

Octave69

List references

SearchIn the docs only

Brings back the customer references stored in Octave, bundle by bundle. The next module can pick the one closest to a prospect's profile.

When to use it

when a deal needs a reference from the same sector and you want to choose from the full set.

Watch out

customer names travel with this data; keep the destination private.

Octave70

List resources

SearchIn the docs only

Returns the resources uploaded to Octave. Think of it as the inventory: it tells you what is there, while Get a resource reads a single one in detail.

When to use it

when you check which documents Octave already holds before adding new ones with Create a resource.

Watch out

to look for resources by content rather than list them all, Search resources is the closer fit.

Octave71

List segments

SearchIn the docs only

Hands you every segment defined in Octave as a list of bundles. Map them into a lookup table or a CRM picklist so everyone uses the same segments.

When to use it

when the CRM segment field must match what Octave knows.

Watch out

deleted segments disappear from the list; records that used them elsewhere will not be cleaned up by Make.

Octave72

List services

SearchIn the docs only

Reads all the services stored in Octave and returns one bundle each. It is the read side of your services catalog.

When to use it

when a proposal scenario needs to show the client the full range of services on offer.

Watch out

services and products are separate lists in Octave; call List products too if your offer mixes both.

Octave73

List solutions

SearchIn the docs only

Returns the solutions recorded in Octave, so your scenario can pick the right one or copy the whole set elsewhere.

When to use it

when a need captured in a form has to be matched against every solution you document.

Watch out

several solutions can match the same need; decide in your scenario which one wins before sending anything.

Octave74

List use cases

SearchIn the docs only

Gives your scenario all the use cases saved in Octave, one per bundle. Good for building an index or checking coverage.

When to use it

after Generate use cases, to review everything Octave now holds before sharing it with the sales team.

Watch out

if the list is long, aggregate before sending a message, or each use case triggers its own notification.

Octave75

Make an API call

ActionIn the docs only

When the listed modules stop short, this one lets you call any endpoint of the Octave API from your scenario, reusing the same connection. No separate key to set up.

When to use it

when you need an Octave feature that none of the 101 modules exposes.

Watch out

you write the request yourself, so keep the Octave API documentation open and test with Run once.

Octave76

Run a call prep agent

ActionIn the docs only

Launches Octave's call prep agent from a scenario, so preparation for a sales call can start as soon as a meeting exists somewhere else. The agent's output comes back for the next module.

When to use it

when a meeting is booked in your calendar tool and the rep should get a prep brief attached.

Watch out

Octave's doc warns its Make pages are AI-generated and may contain mistakes; check the agent's output before it reaches a customer.

Octave77

Run a content agent

ActionIn the docs only

Starts the content agent in Octave and returns what it wrote. That puts drafted copy inside your scenario, ready to be stored, reviewed or sent.

When to use it

when a new product or campaign record should come with a first draft of copy.

Watch out

pair it with Get a brand voice or Apply a brand voice if tone matters; the agent alone may not pick the voice you expect.

Octave78

Run a prospector agent

ActionIn the docs only

Kicks off Octave's prospector agent and brings its findings into Make. Your scenario can then push them to a CRM, a sheet or a review channel.

When to use it

when a new target account is added and the team wants prospects surfaced without manual research.

Watch out

every result it returns can flow into later steps; review the Run once output before sending anything outward.

Octave79

Run a qualify company agent

ActionIn the docs only

Asks Octave to qualify a company and hands the verdict to your scenario. The next modules can then treat good fits and the rest differently.

When to use it

when a company signs up or fills a form and sales only wants the qualified ones.

Watch out

treat the verdict as a suggestion to review, not a final decision, since the doc gives no detail on how it is reached.

Octave80

Run a qualify person agent

ActionIn the docs only

Runs Octave's person qualification agent on a contact and returns the outcome. It differs from the company version: here the subject is the individual, not their employer.

When to use it

when a new contact arrives from a webinar or form and you want to know whether a rep should follow up.

Watch out

personal data goes to Octave with each run; make sure that fits your privacy rules.

Octave81

Run a sequence agent

ActionIn the docs only

Hand a contact to your Octave sequence agent and get back the outreach it drafts, ready to pass to the next module of your scenario (the automation you build in Make).

When to use it

a new lead lands in your CRM and you want a first draft of the follow-up messages without opening Octave.

Watch out

the doc gives no field list for this module, so open it in Make and read what it asks for before mapping data.

Octave82

Run a workflow

ActionIn the docs only

Starts one of your Octave workflows from inside Make, so a workflow you already built in Octave runs without anyone clicking in the app.

When to use it

a deal changes stage in another tool and you want Octave to take over with a workflow it already knows.

Watch out

starting a workflow and knowing when it has finished are two separate modules; Get a workflow run status reads the outcome.

Octave83

Run an agent (async)

ActionIn the docs only

Launches an Octave agent and lets the scenario move on without waiting for the answer, which keeps long agent jobs from holding up the rest of the flow.

When to use it

pick it over the regular agent modules when the result can come later and you would rather check it with Get an async agent run status.

Watch out

judging by its name, this module only launches the run; fetch the answer later with the status module.

Octave84

Run an enrich company agent

ActionIn the docs only

Gives Octave a company and receives a richer profile of it, which you can then write into a CRM, a sheet or a Slack message with the next module.

When to use it

right after a form brings in a company name and your sales team needs context before the first call.

Watch out

each company you send is one bundle, so a list of accounts means one run per account, each counted as an operation on your Make plan.

Octave85

Run an enrich person agent

ActionIn the docs only

Sends a person to the Octave enrichment agent and returns what it found about them, turning a bare name and email into a contact your reps can actually work with.

When to use it

a webinar signup or a demo request arrives and you want the record completed before routing it to a rep.

Watch out

pair it with Run an enrich company agent when you need both sides; this module only covers the individual, not the employer.

Octave86

Search context

SearchIn the docs only

Looks through the context stored in your Octave workspace and returns the pieces that match your query, so a later module can use them in a message or a document.

When to use it

before generating an email, when you want the scenario to pull the right proof or product angle for this prospect.

Watch out

a search can return several items; each one travels as a separate bundle, so add a filter if only one match matters.

Octave87

Search resources

SearchIn the docs only

Finds the resources saved in Octave that match what you type, handing each result to the rest of the scenario as its own item.

When to use it

you want to check whether a resource already exists before creating it again with Create a resource.

Watch out

several matches mean several bundles downstream; if the next step is an update, make sure it targets the one you meant.

Octave88

Toggle default brand voice

ActionIn the docs only

Switches which brand voice Octave treats as the default, so the content its agents write afterward follows the tone you picked.

When to use it

a campaign for a specific market starts and the team needs every generated message to use that market's voice.

Watch out

a default is shared by whatever relies on it in Octave, not tied to your scenario, so check with your team before switching it from an automation.

Octave89

Update a brand voice

ActionIn the docs only

Edits a brand voice that already exists in Octave, keeping every agent that relies on it aligned with the wording you now want.

When to use it

your positioning changes after a rebrand and the saved voice should reflect the new tone without being rebuilt from scratch.

Watch out

you need the voice's identifier first; Get a brand voice or List brand voices gives it to you in an earlier module.

Octave90

Update a buying trigger

ActionIn the docs only

Changes the details of a buying trigger already saved in Octave, so the signals your agents watch for stay accurate as your market shifts.

When to use it

sales notices a signal has changed meaning and updates it in a shared sheet; Make carries the edit over to Octave.

Watch out

fetch the trigger first with Get a buying trigger or List buying triggers, otherwise the module has no idea which one to edit.

Octave91

Update a competitor

ActionIn the docs only

Refreshes a competitor profile in Octave, so battle cards and agent answers mention what the rival really offers today.

When to use it

a teammate logs a new competitor feature in your CRM or a form and you want Octave updated without retyping it.

Watch out

it edits the record it is pointed at and nothing else; pick the right competitor with List competitors before this step.

Octave92

Update a persona

ActionIn the docs only

Rewrites a persona stored in Octave, which keeps every message aimed at that buyer type in line with what your team has learned.

When to use it

interviews or win/loss notes reveal a new pain point and the persona needs it before the next outreach goes out.

Watch out

updating does not create; if the persona might not exist yet, check with Get a persona and route the missing ones to Create a persona.

Octave93

Update a playbook

ActionIn the docs only

Adjusts a playbook already in Octave, so the agents that follow it pick up the new steps or messaging right away in their next run.

When to use it

a sales manager approves a revised approach and wants it applied without opening the Octave editor.

Watch out

find the playbook's identifier with List playbooks first; a wrong ID edits the wrong playbook, and the scenario will not warn you.

Octave94

Update a product

ActionIn the docs only

Keeps a product record in Octave current, which matters because agents draw on it whenever they describe what you sell.

When to use it

a launch or pricing page change is logged in your product tool and Octave should reflect it before new emails are written.

Watch out

map only the fields you mean to change and check the result with Run once, the editor button that runs the scenario a single time.

Octave95

Update a proof point

ActionIn the docs only

Edits a proof point in Octave, so the claims and results your agents quote stay the ones your team can still stand behind.

When to use it

marketing validates a new result or retires an old one and the change should reach Octave from the same approval step.

Watch out

pull the proof point with Get a proof point first to see its current content before overwriting it.

Octave96

Update a reference

ActionIn the docs only

Updates a customer reference stored in Octave, making sure the stories your agents cite reflect where that account stands now.

When to use it

an account renews, grows or churns in your CRM and its reference in Octave needs to follow.

Watch out

a reference that should no longer be cited may call for Delete a reference instead; updating keeps it available to agents.

Octave97

Update a segment

ActionIn the docs only

Reshapes a segment in Octave, changing how your target groups are described so the agents address each group with the right framing.

When to use it

the team redraws its target market and wants Octave's segments to match what the CRM now says.

Watch out

this module needs the segment's identifier; List segments earlier in the scenario is the simplest way to get it.

Octave98

Update a service

ActionIn the docs only

Modifies a service entry in Octave, so any agent describing what you deliver uses the current scope and wording.

When to use it

a consulting offer is reworked and the new description lives in a doc or sheet that Make can read.

Watch out

Make runs this once per bundle; if the source sends several rows for the same service, only the last write stays.

Octave99

Update a solution

ActionIn the docs only

Brings a solution record in Octave up to date, keeping the way agents pitch a combined offer consistent with your latest positioning.

When to use it

product and sales agree on a new angle for a solution and want it pushed to Octave from their shared tracker.

Watch out

Generate a solution creates fresh content; this module edits an existing one, so pick it only when the solution is already saved.

Octave100

Update a use case

ActionIn the docs only

Edits a use case saved in Octave, sharpening the examples your agents lean on when they explain why a prospect should care.

When to use it

customer feedback shows a use case is described too vaguely and the team rewrites it in its content tracker.

Watch out

check the use case with Get a use case before overwriting it; the scenario does not keep a copy of the old text.

Octave101

Update an agent

ActionIn the docs only

Changes the settings of an existing Octave agent, so you can tune how it behaves without rebuilding it or leaving your scenario.

When to use it

your team tests a new instruction set and wants the agent concerned to adopt it.

Watch out

other scenarios that call this agent will pick up the change too; List agents helps confirm which one you are editing.

Need help

Need help automating Octave with Make?

A person reads every message.

FAQ

Octave and Make: common questions

01Is the Octave Make integration free?

Yes, on the Make side. Octave is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. On the Octave side, you still need an active account; its subscription terms are on the Octave pricing page.

02What do you need to connect Octave to Make?

An active Octave account and an API key. You get the key in Octave under the Developers tab in the top menu, where a button generates a new key for your workspace; copy it as soon as it appears. Then, in Make, add any Octave module, click Create a connection, give it a name if you like and paste the key. That single connection serves every Octave module in all your scenarios, so the setup only happens once per workspace.

03Does the Octave Make integration react in real time?

No, because Octave has no trigger module in Make: none of its 101 modules can start a scenario. You have two ways to start anyway. Either a trigger from another app opens the flow, for example a CRM or a form, and the Octave modules follow it. Or you set a schedule on the first module, every 15 minutes by default, down to 1 minute on a paid plan. An instant trigger of another app, which calls Make through a webhook, is the closest you get to real time.

04What if an Octave module is missing in Make?

Use Make an API call. It is part of the Octave app in Make and lets the scenario call any endpoint of the Octave API with the same connection, so you are not limited to the listed modules. Before building on it, keep one warning in mind: the Octave documentation in Make is AI-generated content based on the official Octave documentation and may contain mistakes. Check important details against the vendor documentation, or contact Octave directly when something does not behave as described.

05Should you use Make or n8n for Octave?

It depends on the tool your team already works in. On Make, Octave comes with 101 modules, including Make an API call for the rest, and works from the Free plan within its limits. n8n often has a node for the same app, so check its catalog before choosing. The fair test is simple: list the Octave actions your scenario needs, see which tool covers them without workarounds, and pick the editor your team will actually maintain.

Generate your API key in Octave

Add an Octave module in Make

Paste the key and save

Create the scenario

Set the starting module

Add the Octave agent

Test with Run once

Schedule and switch it on

Need help automating Octave with Make?