Octave to Airtable, decision makers found by role
Prospecting by job title sounds efficient. In practice, it’s how you end up emailing the wrong “VP,” missing the actual owner, and wondering why replies are slow (or nonexistent).
This is the kind of mess SDR teams feel every day, but ABM marketers and RevOps folks cleaning up contact tables deal with it too. With this Octave Airtable automation, you stop guessing based on titles and start finding people by what they’re responsible for.
Below you’ll see exactly how the workflow runs in n8n, what it outputs into Airtable, and where the real time savings show up once it’s running.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Octave to Airtable, decision makers found by role
flowchart LR
subgraph sg0["Manual Workflow Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Workflow Trigger", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Get Target Accounts"]
n2@{ icon: "mdi:cog", form: "rounded", label: "Discover Relevant Contacts", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Save Discovered Contacts"]
n1 --> n2
n0 --> n1
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n1,n3 database
classDef customIcon fill:none,stroke:none
class n1,n3 customIcon
The Problem: Title-based prospecting misses real owners
Job titles are a rough guess, not a reliable signal. One company’s “Head of Platform” is another company’s “VP Engineering,” and plenty of buying decisions never sit with the most obvious title anyway. So your list looks fine on paper, but outreach performance tells the truth. You end up over-targeting senior titles that aren’t hands-on, under-targeting the people who actually own the workflow, and wasting hours on research that still produces shaky matches. It’s frustrating, because you’re doing “the right work,” but the inputs are wrong.
The friction compounds. Here’s where it usually breaks down.
- You spend about 10 minutes per account cross-checking titles, org charts, and LinkedIn, and it still feels like a coin flip.
- Your contact table fills up with “close enough” roles, which means more bounces, more unsubscribes, and more internal finger-pointing.
- As soon as you scale to a few hundred accounts, manual research becomes the bottleneck and campaigns slip.
- Reps lose trust in the list, so they ignore it and go back to one-off prospecting.
The Solution: Octave finds stakeholders by responsibilities, then writes them to Airtable
This workflow flips your prospecting logic around. Instead of asking, “Who has the right title?”, it asks, “Who owns the responsibilities tied to our use case?” It starts by pulling your target account list from Airtable (typically company name and domain). For each company, Octave’s prospector agent analyzes context and organization signals to discover the stakeholders that match your personas, role responsibilities, and KPIs. Then n8n takes the structured contact output (names, role context, LinkedIn profile details, and relevance) and writes the results back into Airtable so your team has a clean, action-ready contact table. No spreadsheet ping-pong. No half-researched guesses.
The workflow kicks off manually (so you can test safely), then reads accounts from Airtable, hands each account to Octave for contact discovery, and finally records the found contacts in your destination table. The end state is simple: a list your reps can actually work from.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you’re working a list of 100 target accounts for a new campaign. Manually, even a “quick” pass is maybe 10 minutes per account to find 2–3 likely stakeholders, which is roughly 16 hours of research. With this workflow, you trigger the run once, Octave prospects based on your personas, and the contacts land in Airtable as they’re found. Realistically you’ll spend about 30 minutes setting criteria and reviewing the output, not days stuck in tabs.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Airtable for your account and contacts tables.
- Octave to prospect contacts by responsibilities.
- Octave API key (get it from your Octave workspace settings).
Skill level: Beginner. You’ll connect Airtable and Octave, then map a few fields.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You start the run in n8n. The workflow uses a manual trigger, which is great for validating your table IDs and Octave settings before you schedule anything.
Airtable provides the target accounts. n8n reads your account list (company name and domain are the key fields), so you’re not copying CSVs around or maintaining two “sources of truth.”
Octave prospects the right people. The prospector agent looks for stakeholders based on the personas and responsibility signals you care about, not just whatever title happens to be on LinkedIn this month.
Airtable becomes the clean output layer. n8n writes discovered contacts into your contacts table, so your team can filter, assign, and sequence without reformatting anything.
You can easily modify the personas and relevance thresholds to prioritize different buying roles based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow manually to validate your Airtable inputs and prospecting results before automation.
- Add and open Manual Start Trigger as the first node in the flow.
- Confirm there are no parameters required in Manual Start Trigger.
- Connect Manual Start Trigger to Retrieve Target Accounts to match the execution flow.
Step 2: Connect Airtable for Target Accounts
Pull account records from Airtable to supply company domains for prospecting.
- Open Retrieve Target Accounts and set Operation to
search. - Select the Airtable Base as
Your Target Account Baseand the Table asTarget Accounts List. - Credential Required: Connect your airtableTokenApi credentials.
- Ensure the output includes a Company Domain field used downstream.
Step 3: Set Up Prospect Relevant Contacts
Use Octave to prospect contacts based on each company domain.
- Open Prospect Relevant Contacts and set Operation to
runProspector. - Set Agent ID to
[YOUR_ID](replace with your Octave agent ID). - Set Company Domain to
{{ $json['Company Domain'] }}. - Credential Required: Connect your octaveApi credentials.
Step 4: Configure Record Found Contacts
Write the top prospect result into Airtable for follow-up and tracking.
- Open Record Found Contacts and set Operation to
create. - Select the Airtable Base as
Your Target Account Baseand the Table asDiscovered Contacts List. - Map the columns using expressions:
Job Title →{{ $json.contacts[0].contact.title }}
Last Name →{{ $json.contacts[0].contact.lastName }}
First Name →{{ $json.contacts[0].contact.firstName }}
Company Name →{{ $json.contacts[0].contact.companyName }}
Company Domain →{{ $json.contacts[0].contact.companyDomain }}
LinkedIn Profile →{{ $json.contacts[0].contact.profileUrl }} - Credential Required: Connect your airtableTokenApi credentials.
$json.contacts[0]. Consider adding a filter later if Octave returns empty results.Step 5: Test and Activate Your Workflow
Run the workflow manually and verify a complete pass from Airtable to Octave and back to Airtable.
- Click Execute Workflow from Manual Start Trigger.
- Verify that Retrieve Target Accounts outputs records with Company Domain values.
- Confirm Prospect Relevant Contacts returns a contacts array.
- Check Airtable to confirm Record Found Contacts created a new row in
Discovered Contacts List. - Once validated, toggle the workflow to Active for production use.
Common Gotchas
- Airtable credentials can expire or the token may not have access to the right base. If things break, check the n8n Airtable credential and confirm the base/table permissions in Airtable first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Octave runs on personas and responsibility definitions you set. If your prospector agent is too generic, you’ll get “fine” contacts that still need editing, so tighten personas early and save yourself the headache.
Frequently Asked Questions
About 30 minutes if your Airtable base is ready.
No. You’ll connect Octave and Airtable, then map fields in n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Octave API usage based on your plan.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Update your Octave prospector agent personas and responsibility signals, then adjust the field mapping in the “Record Found Contacts” Airtable step so the role context lands where your reps expect it. Common customizations include prioritizing management level, limiting contacts per account, and setting a minimum relevance threshold so you don’t flood the table.
Usually it’s an expired or incorrect Octave API key, so regenerate it in your Octave workspace and update the credential in n8n. It can also fail if you pasted the wrong prospector agent ID or the workspace doesn’t have access to that agent. If you’re running large batches, you may hit API limits, which looks like intermittent failures or empty results. In that case, reduce batch size and rerun the accounts that failed.
On n8n Cloud Starter, you can run a few thousand executions per month, and higher plans support more. If you self-host, there’s no execution limit, but your server and Octave quota become the practical ceiling. For most teams, processing a list of a few hundred accounts in a run is realistic, then you refine and rerun weekly.
Often, yes. n8n is easier to adapt when you want branching logic (different personas by segment), deduping rules, or richer field transforms before writing to Airtable, and you can self-host if volume gets high. Zapier and Make are fine for simple “send data from A to B” flows, but prospecting outputs usually need a bit more shaping to stay usable. If you plan to route results to Slack, assign owners, or run batches on a schedule, n8n tends to feel less cramped. Talk to an automation expert if you want a quick recommendation based on your volume and tools.
Once this is running, your list stops being a debate and starts being a workflow. The automation handles the repetitive prospecting grind, so your team can focus on outreach that actually converts.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
