Discover decision makers by responsibilities (not titles) with Octave & Airtable
Discover relevant contacts from target accounts using Octave intelligent prospecting
Who is this for?
Sales development teams, account-based marketing professionals, and RevOps teams who are tired of generic job title filtering that misses the real decision makers. Built for teams that need to find the right people based on actual responsibilities and business context, not just titles on LinkedIn.
What problem does this solve?
Most prospecting tools are flying blind when it comes to finding the right contacts. You search for "VP of Engineering" but miss the "Head of Platform" who actually owns your use case. You filter by "Marketing Director" but the "Growth Lead" is the real buyer. Traditional prospecting relies on job title matching, but titles vary wildly across companies. This workflow uses Octave's context engine to find contacts based on who actually does the work your solution impacts, regardless of their specific job title.
What this workflow does
Target Account Processing:
- Reads target account lists from Airtable (or other data sources)
- Processes company domains for intelligent contact discovery
- Handles batch processing for multiple target accounts
Context-Aware Contact Discovery:
- Uses Octave's prospector agent to find relevant stakeholders within target organizations
- Leverages your defined personas to identify the right people based on responsibilities, not just titles
- Analyzes organizational structure, role responsibilities, and KPIs to match contacts to your solution
- Discovers decision makers and influencers who might be missed by traditional job title searches
Structured Contact Output:
- Returns discovered contacts with complete profile information
- Includes LinkedIn profiles, contact details, and role context
- Organizes contacts by relevance and decision-making authority
- Exports contact lists back to Airtable for sales team action
Setup
Required Credentials:
- Octave API key and workspace access
- Airtable API credentials (or your preferred contact management platform)
- Access to your target account list
Step-by-Step Configuration:
-
Set up Target Account Source:
- Add your Airtable credentials to n8n
- Replace
your-airtable-base-idandyour-accounts-table-idwith your actual account list - Ensure your account list includes company domains for prospecting
- Configure trigger method (manual, scheduled, or webhook-based)
-
Configure Octave Prospector Agent:
- Add your Octave API credentials in n8n
- Replace
your-octave-prospector-agent-idwith your actual prospector agent ID - Configure your prospector with relevant personas and role definitions
- Test prospecting with sample companies to verify contact quality
-
Set up Contact Output Destination:
- Replace
your-contacts-table-idwith your target contact list table - Configure field mapping between Octave output and your contact database
- Set up data validation and deduplication rules
- Test contact creation and data formatting
- Replace
-
Customize Contact Selection:
- Configure which personas to prioritize in your prospector agent
- Set relevance thresholds for contact discovery
- Define organizational levels to target (individual contributors vs. management)
- Adjust contact volume per account based on your outreach capacity
Required Account List Format: Your Airtable (or data source) should include:
- Company Name
- Company Domain (required for prospecting)
- Account status/priority (optional)
- Target personas (optional)
How to customize
Prospector Configuration: Customize contact discovery in your Octave prospector agent:
- Persona Targeting: Define which of your Library personas to prioritize when prospecting
- Role Responsibilities: Configure the specific responsibilities and KPIs that indicate a good fit
- Organizational Level: Target specific levels (IC, manager, director, VP, C-level) based on your solution
- Company Size Adaptation: Adjust prospecting approach based on organization size and structure
Contact Selection Criteria: Refine who gets discovered:
- Decision-Making Authority: Prioritize contacts with budget authority or implementation influence
- Problem Ownership: Focus on roles that directly experience the pain points your solution solves
- Technical Influence: Target contacts who influence technical decisions if relevant to your offering
- Process Ownership: Identify people who own the processes your solution improves
Data Integration: Adapt for different contact management systems:
- Replace Airtable with your CRM, database, or spreadsheet system
- Modify field mapping to match your contact database schema
- Add data enrichment steps for additional contact information
- Integrate with email platforms for immediate outreach
Batch Processing: Configure for scale:
- Adjust processing volume based on API limits and prospecting quotas
- Add scheduling for regular account list updates
- Implement error handling for accounts that can't be prospected
- Set up monitoring for prospecting success rates
Use Cases
- Account-based marketing contact list generation
- Sales territory planning and contact mapping
- Competitive displacement campaign targeting
- Product expansion within existing customer accounts
- Event-based prospecting for specific personas
- Market research and competitive intelligence gathering
Discover Decision-Makers by Responsibilities (Not Titles) with Octave & Airtable
This n8n workflow provides a starting point for integrating Airtable data. While the full scope of its intended use with "Octave" for discovering decision-makers by responsibilities isn't explicitly defined in the current JSON, this template sets up a manual trigger to initiate an Airtable data operation.
What it does
This workflow, in its current form, performs the following steps:
- Manually Triggered: The workflow is initiated by a user manually clicking the "Execute workflow" button within the n8n interface.
- Airtable Interaction: It then connects to Airtable, ready to perform an operation (e.g., retrieve records, create new ones, update existing data). The specific operation is not configured in this base JSON.
- Sticky Note: A sticky note is included, likely for documentation or temporary comments within the workflow design.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Airtable Account: An Airtable account with an API key and access to the base/table you intend to interact with.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Airtable Credentials:
- Click on the "Airtable" node.
- In the "Credentials" section, select an existing Airtable credential or create a new one.
- For a new credential, provide your Airtable API Key.
- Configure Airtable Operation:
- Within the "Airtable" node, select the desired "Operation" (e.g., "Get All", "Create", "Update").
- Specify the "Base ID" and "Table Name" you wish to interact with.
- Configure any additional parameters relevant to your chosen operation (e.g., filters, fields, records).
- Execute the Workflow: Click the "Execute workflow" button in the n8n editor to run the workflow manually. You can also activate the workflow to run on a schedule or via a webhook if you change the trigger node.
Related Templates
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns Youβll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
π Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πππ¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. π§© Step 2: Fetches release metadata including version, tag, and publish date. π¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. π Step 4: Retrieves FAQ or documentation data from Notion. π Step 5: Merges GitHub and Notion data to calculate documentation drift. π Step 6: Flags SDKs whose documentation is over 30 days out of date. β οΈ Step 7: Sends detailed Slack alerts to notify responsible teams. π Key Benefits β Keeps SDK documentation aligned with product releases β Prevents outdated information from reaching users β Provides centralized release tracking in Google Sheets β Sends real-time Slack alerts for overdue updates β Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.
Automate Gmail responses with GPT and human-in-the-loop verification
Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com