Build a LinkedIn hiring-signal data table with Apify and Slack
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on a schedule (every 12 hours) (plus 1 other trigger). Along the way it connects Slack and Apify (community).
How it runs
Trigger: On a schedule (every 12 hours) (plus 1 other trigger).
- Configure Target Accounts (Edit Fields (Set)): sets or maps fields
- Run Curly LinkedIn Jobs Scraper (Apify): run actor and get dataset
- Normalize Hiring Signals (Code): runs custom JavaScript code
- Remove Same-Run Duplicates (Remove Duplicates): removes duplicate items
- Keep Jobs Not Yet Stored (Data table): row not exists
- Store New Hiring Signals (Data table): uses Data table
- Build Optional Company Digests (Code): runs custom JavaScript code
- Optional Slack Digest (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Run Curly LinkedIn Jobs Scraper).
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Apify
@apify/n8n-nodes-apify.apify - Code
n8n-nodes-base.code - Remove Duplicates
n8n-nodes-base.removeDuplicates - Data table
n8n-nodes-base.dataTable - Slack
n8n-nodes-base.slack
From the author
Quick overview Monitor selected companies for new LinkedIn jobs with Curly’s Apify Actor. The workflow normalizes and deduplicates results, stores unseen roles in a reusable n8n Data Table, and can optionally send one Slack digest per company. How it works 1.…