Enrich Google Sheets Domains with Verified Decision Makers (Apify)

Enrich Google Sheets domains with verified decision-maker contacts using Apify

This n8n workflow pulls company domains from your Google Sheets, runs the Apify Decision Maker Finder to find verified decision makers, and writes the results back into your Sheets—complete with per-domain classifications and an audit trail.

What this workflow does

• Runs manually and loads configuration values such as your spreadsheet ID, the target persona, batch size, and Apify polling limits.
• Reads domains from an Inputs sheet and keeps only rows where the status is blank/READY, then normalizes and deduplicates domains.
• Flags valid rows as IN_PROGRESS in Google Sheets to lock the batch before enrichment begins.
• Starts the Apify Decision Maker Finder Actor with email verification enabled and a maximum run charge.
• Polls Apify until the run succeeds, fails, or reaches the polling limit.
• Downloads the Apify dataset on success and classifies every requested domain, including cases where Apify returns missing/empty results (e.g., outcomes like VERIFIED_DM_REVIEW or NO_BILLABLE_RESULT).
• Upserts results into a Results sheet and updates each original Inputs row with the final classification, processed timestamp, and any error message.
• Writes batch-level logs to a Run_Log sheet; on failures it records a failed run, marks affected Inputs rows with the failure class, and stops with an error.

Use cases

• SaaS teams enriching leads from a domain list stored in Google Sheets.
• Automation engineers building a repeatable “domain → verified decision maker” enrichment pipeline.
• Operations teams maintaining an audit trail for each enrichment run via a Run_Log sheet.

Technical details

• Google Sheets: Inputs, Results, and Run_Log upserts/updates.
• Apify: Decision Maker Finder Actor with email verification enabled and polling until completion.
• n8n nodes/tools mentioned: if, set, code, wait, and HTTP Request, plus workflow annotations (sticky note).