Track alumni job changes with Coresignal, Google Sheets and Slack
UnknownWhat this workflow does
This workflow has 15 nodes and runs on a schedule (every week at 08:00). Along the way it connects Google Sheets, Slack and Coresignal Api (community).
How it runs
Trigger: On a schedule (every week at 08:00).
- Read Employees from Sheets (Google Sheets): uses Google Sheets
- Filter: keeps only the items that match a condition
- Loop Over Alumni Profiles (Loop Over Items (Split in Batches)): loops over the items in batches
- Set Summary Field (Edit Fields (Set)): sets 1 field: summary
- Transform Profile URL (Code): runs custom JavaScript code
- Search Employee in Coresignal (Coresignal): search es dsl
- Extract IDs from Response (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Collect Employee Details (Coresignal): uses Coresignal
- Log No Match Found (Code): runs custom JavaScript code
…plus 4 more steps. See the full node list below.
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 n8n-nodes-coresignal-api is verified or supports 3.0 (used in Search Employee in Coresignal, Collect Employee Details).
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Filter
n8n-nodes-base.filter - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Coresignal
n8n-nodes-coresignal-api.coresignal - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs weekly, reads alumni profile URLs from Google Sheets, looks up matching employee profiles in Coresignal, detects job changes based on the current active employer, posts alerts to Slack when a change is confirmed, and writes…