Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Who is this for This template is for sales teams, SDRs, and revenue operations professionals who need to quickly find mobile phone numbers from a list of LinkedIn profile URLs or work email address...
n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.splitinbatches, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Alex Berman.
Original n8n.io sourceThis template is for sales teams, SDRs, and revenue operations professionals who need to quickly find mobile phone numbers from a list of LinkedIn profile URLs or work email addresses. If your team relies on cold calling as part of outreach and wants to automate the enrichment step, this workflow saves hours of manual lookup.
The workflow reads a list of LinkedIn URLs or work emails from a Set node, submits them to the ScraperCity Mobile Finder API, then polls asynchronously until results are ready. Once complete, it downloads the results, parses each contact record, removes duplicates, and posts a formatted Slack alert to your sales team channel with the discovered mobile numbers.
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 | Find mobile numbers with ScraperCity from LinkedIn and notify sales in Slack |
|---|---|
| Complexity | advanced |
| Nodes | 24 |
| Categories | Lead Generation |
| Author | Alex Berman |
| Published | 27 Mar 2026 |
Use the JSON export at /data/workflows/14383/14383.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.
Who is this for This template is for sales teams, SDRs, and revenue operations professionals who need to quickly find mobile phone numbers from a list of LinkedIn profile URLs or work email address...
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.