Block 1 - Manual Trigger
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Introduction Manual LinkedIn data collection is time consuming, error prone, and results in inconsistent data quality across CRM/database records. This workflow is great for organizations that stru...
n8n-nodes-base.manualtrigger, n8n-nodes-base.nocodb, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.code, n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Guido X Jansen.
Original n8n.io sourceManual LinkedIn data collection is time-consuming, error-prone, and results in inconsistent data quality across CRM/database records.
This workflow is great for organizations that struggle with:
Each URL scraped by Apify costs $0.01 to get all the data above. Apify charges per scrape, regardless of how much dta or fields you extract/use.
NocoDB Field name
LinkedIn
NocoDB Field names
linkedin_full_name
linkedin_first_name:
linkedin_headline:
linkedin_email:
linkedin_bio:
linkedin_profile_pic
linkedin_current_role
linkedin_current_company
linkedin_country
linkedin_skills
linkedin_company_website
linkedin_experiences
linkedin_personal_website
linkedin_publications
linkedin_scrape_error_reason
linkedin_scrape_last_attempt
linkedin_scrape_status
linkedin_last_modified
Technically you also need an Id field, but that is always there so no need to add it :)
- Copy the workflow JSON from the template
- In n8n, click "Add workflow" → "Import from JSON"
- Paste the workflow and click "Import"
- Click on any NocoDB node in the workflow
- Add new credentials → "NocoDB Token account"
- Enter your NocoDB API token (found in NocoDB → User Settings → API
Tokens) - Update the projectId and table parameters in all NocoDB nodes
- Create an Apify account at apify.com
- Generate an API token (Settings → Integrations → API)
- In the workflow, update the Apify token in the "Get Scraper Results"
node - Configure HTTP Query Auth credentials with your token
- Review the "Transform & Sanitize Data" node
- Update field mappings to match your NocoDB table structure
- Ensure these fields exist in your table:
- LinkedIn (URL field)
- linkedin_headline, linkedin_full_name, linkedin_bio, etc.
- linkedin_scrape_status, linkedin_last_modified
- In "Get Guests with LinkedIn" node
- Adjust the filter to match your requirements
- Default: (LinkedIn,isnot,null)~and(linkedin_headline,is,null)
- Click "Execute Workflow" with Manual Trigger
- Monitor execution for any errors
- Verify data is properly updated in NocoDB
- Configure the Schedule Trigger node (default: monthly)
- Toggle the workflow to "Active"
- Monitor executions in n8n dashboard
4. Error Handling Enhancement
These customizations allow the workflow to adapt from simple contact enrichment to complex data pipeline scenarios across various industries and use cases.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Enrich LinkedIn profiles in NocoDB CRM with Apify scraper |
|---|---|
| Complexity | advanced |
| Nodes | 21 |
| Categories | Lead Generation |
| Author | Guido X Jansen |
| Published | 24 Jun 2025 |
Use the JSON export at /data/workflows/5258/5258.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Introduction Manual LinkedIn data collection is time consuming, error prone, and results in inconsistent data quality across CRM/database records. This workflow is great for organizations that stru...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation use case.