Turn company research into a simple, repeatable flow for HR and talent teams. Links stored in Airtable are fetched, cleaned, summarized with AI, and sent to a webhook for easy reporting. The goal is faster employer insights with less manual work.

Here is how it runs end to end. A manual start loads an Airtable table with company profile links. Items move through a loop with a short pause to control speed. Each non empty link goes to Bright Data, which fetches the page content. The content is converted to HTML and also transformed into plain text. A Google Gemini chain extracts key details and a summarization chain creates a short brief. An AI Agent formats the final result as structured JSON and posts it to a webhook. The loop continues until all records are processed.

To set it up, you need Airtable with a table that includes a Link field, a Bright Data zone, a Google Gemini API key, and a webhook URL. Expect big time savings when checking many company pages and cleaner summaries for quick reading. Use it for employer brand research, competitor tracking, and talent market scans. After connecting credentials and URLs, run the test and review the webhook output for quick validation.

• Airtable reader pulls company links from a defined base and table
• Loop and wait nodes pace requests to avoid rate limits and blocks
• HTTP request posts to Bright Data using your zone to fetch page content
• Markdown and extractor chain convert raw content to clean text and HTML
• Google Gemini summarization builds short, readable briefs
• AI Agent formats structured JSON and sends it to a webhook endpoint
• If node skips empty links for cleaner runs and fewer errors
• Webhook notifications confirm HTML conversion and downstream delivery

• Reduce manual research from 4 hours to 15 minutes
• Automate up to 90 percent of repetitive data collection
• Improve data accuracy by 60 percent with AI extraction
• Handle 200 plus company pages in one run without extra effort
• Connect Airtable, Bright Data, Google Gemini and webhooks in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Airtable, Bright Data, Google Gemini and Webhook.site. See the Tools Required section above for links to create accounts with these services.
3. In Airtable, create a base and a table with at least two fields: Tab and Link. Fill the Link field with company profile URLs. Keep field names exactly as used in the sample.
4. In the n8n credentials manager, open the Airtable node, choose 'Create new credential' for Airtable Personal Access Token, and follow the on screen steps. Use a token with access to the base that holds your table.
5. Open the Bright Data HTTP Request node, click 'Create new credential' for Header Auth, then follow the on screen steps to add your Bright Data API token. Do not hardcode secrets in the node.
6. Double click the 'Set Bright Data Zone' node and enter your zone value as provided in your Bright Data account. Save the change.
7. Open the Google Gemini nodes and click 'Create new credential' for Google Gemini API. Follow the on screen steps to add your API key from Google AI Studio.
8. Replace the webhook URLs in both webhook request nodes with your own endpoint. You can use a temporary URL from Webhook.site for testing, then swap it with your production endpoint later.
9. Open the Airtable node and select your base and table. Confirm the Link field is mapped correctly in the downstream nodes.
10. Check the Wait node settings. Set a short wait time if you want throttling. If using the webhook resume option, copy the resume URL and test it with a simple call after a run starts.
11. Click Test workflow to run. Watch the execution: records should loop, pages should fetch, summaries should generate, and webhook deliveries should appear at your endpoint.
12. If Bright Data calls fail, verify your zone value and API token. If AI steps fail, check your Google Gemini key and usage limits. If Airtable returns empty, confirm field names and base selection. If the webhook shows no data, recheck the URL in both webhook nodes.