LinkedIn Lead Generator

This workflow automates LinkedIn lead generation, scraping post interactions, finding emails, and storing data in PostgreSQL, Airtable, and Lemlist. Key nodes include Initialize Database (creates tables), Daily Trigger (schedules runs), Configure LinkedIn Posts (sets post URLs), Scrape LinkedIn Post (uses Phantombuster API), Process Profiles (normalizes data), Save to Database (stores leads), Find Email with Dropcontact (enriches emails), Add to Airtable/Lemlist (exports leads), and Error Handler (logs errors). It uses Phantombuster, Dropcontact, Airtable, and Lemlist APIs.\n\nSetup Requirements: Install n8n from n8n.io or sign up at cloud.n8n.io. Import the JSON into n8n’s workflow editor. Run Initialize Database once to create the linkedin_leads and processing_errors tables. Set up PostgreSQL credentials in n8n (host, database, user, password). Obtain Phantombuster API key and Agent ID from phantombuster.com (Account > API). Get the Dropcontact API key from dropcontact.io (Account > API). Create an Airtable base at airtable.com, get API key and Base ID from Account settings. Obtain Lemlist API key and Campaign ID from app.lemlist.com (Settings > Integrations). Configure credentials in n8n for each service. Update Configure LinkedIn Posts with valid LinkedIn post URLs. Handle errors like invalid Phantombuster key (401: Unauthorized) or missing Airtable base (404: Base not found).\n\nTesting and Deployment: Import the JSON into n8n. Manually run Initialize Database to create tables. Test with a LinkedIn post URL in Configure LinkedIn Posts. Verify Scrape LinkedIn Post triggers Phantombuster and Save to Database stores profile_url, full_name. Check Find Email with Dropcontact returns an email, and Add to Airtable/Lemlist logs leads. Simulate with curl -X POST http://your-n8n-instance/ -d '{"linkedinPost1":"https://linkedin.com/posts/test"}'. Ensure Error Handler logs errors like {"error_details":"Invalid API key"} to processing_errors. Activate the workflow in n8n for daily 9 AM runs. Monitor logs for rate limits (429) or database connection issues. If data isn’t saved, verify PostgreSQL credentials, API keys, and post URLs. Deploy for automated lead generation.