🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 21, 2026

Slack alerts from Google Sheets for LinkedIn changes

Slack alerts from Google Sheets for LinkedIn changes - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Slack alerts from Google Sheets for LinkedIn changes - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You open LinkedIn to “quickly check” a few profiles… and 45 minutes disappears. Worse, you still miss the one job change that mattered because it happened on a day you didn’t look.

Recruiters feel it when candidates move fast. A sales pipeline feels it when a champion changes roles. And relationship managers end up living in tabs. This LinkedIn change alerts automation moves the monitoring to the background and pushes the important updates straight into Slack.

You’ll learn what the workflow does, what you need to run it, and how the pieces fit together so you can track profile changes without babysitting a spreadsheet.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Slack alerts from Google Sheets for LinkedIn changes

Why This Matters: LinkedIn changes are easy to miss

Tracking LinkedIn changes sounds simple until you try to do it consistently. You start with good intentions: a Google Sheet of prospects, candidates, partners, or influencers. Then the real world happens. People change titles, “Open to work” flips on, new posts go live, and your list gets stale without you noticing. The cost isn’t just time. It’s missed timing. You reach out too late (or with the wrong context), and the moment is gone. Honestly, manual checking is one of those tasks that feels “small” but drains your week in tiny chunks.

It adds up fast. Here’s where it usually breaks down.

  • Someone gets a new role and you find out weeks later, after you’ve sent the old-company pitch.
  • Your team updates the Sheet “when they remember,” which means your database becomes a mix of fresh and outdated records.
  • Important signals (hiring, open-to-work, new posts) don’t show up in your day unless you’re actively hunting for them.
  • Manual copy-paste creates quiet errors: wrong headlines, missing summaries, mismatched profile URLs.

What You’ll Build: A scheduled LinkedIn profile tracker with Slack alerts

This workflow turns a simple Google Sheets list into an always-on LinkedIn watchlist. On a schedule (daily by default), n8n pulls the rows from your “profile sheet,” checks each LinkedIn URL, and fetches fresh profile and post data through an HTTP request (via the Ghost Genius scraping API). It then compares what it just retrieved against what’s already stored in your sheet. If something changed, the workflow sends a Slack message showing the update and then writes the new value back to Google Sheets so your sheet stays current. If nothing changed, it takes the no-op path and moves on quietly. The end result is a clean, living database plus timely Slack pings when a job move or profile edit is worth acting on.

The workflow starts with a scheduled trigger and your Google Sheet as the “source of truth.” From there, it loops through profiles, pulls current profile data and recent posts, and runs change detection. Finally, Slack notifications go out for the specific field that changed, and Google Sheets is updated so future comparisons stay accurate.

What You’re Building

Expected Results

Say you track 50 LinkedIn profiles in a Sheet and you “check them quickly” once a week. If it takes about 2 minutes per profile to load, scan, and update the Sheet, that’s roughly 100 minutes, plus context switching and mistakes (call it about 2 hours). With this workflow, the daily trigger runs automatically and Slack only pings you when something changes. Your “time spent” becomes a few minutes reviewing alerts, while Google Sheets stays updated in the background.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Sheets for your tracking database and fields.
  • Slack to receive change alerts in a channel.
  • Ghost Genius API key (get it from your Ghost Genius dashboard) for LinkedIn profile scraping.

Skill level: Intermediate. You’ll be connecting accounts, adding credentials, and mapping a few fields in Google Sheets and Slack.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A schedule triggers the run. The workflow uses a scheduled trigger (daily in this template) so your tracking happens even when you’re busy or out of office.

Google Sheets provides the list. n8n loads your profile sheet, filters for the rows that should be checked, then prepares those items for processing in batches so you don’t hammer APIs all at once.

LinkedIn data is fetched and compared. HTTP requests pull current profile details and recent posts using your Ghost Genius API key. A change detection step (switch/if logic) decides which field changed, if any, and routes the item down the right path.

Slack is notified and the Sheet is updated. If the first name, headline, summary, experience, hiring/open status, or latest post changes, the workflow sends a Slack message and then writes the new value back to Google Sheets so the next run compares against the latest record.

You can easily modify the schedule and which fields trigger alerts based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Scheduled Daily Trigger

This workflow runs every morning and starts by loading your profile tracker sheet.

  1. Add the Scheduled Daily Trigger node and open its settings.
  2. Set the schedule rule to trigger daily at Trigger At Hour 8.
  3. Connect Scheduled Daily Trigger to Fetch Profile Sheet.

Step 2: Connect Google Sheets

These nodes read and update your profile tracker sheet with new profile data and change detection results.

  1. Open Fetch Profile Sheet and set Document to Copy of Profiles Tracker and Sheet to Profiles.
  2. Open Append New Profiles and confirm Operation is update with Matching Columns set to LinkedIn.
  3. Open Load Existing Records and set Document to Copy of Profiles Tracker and Sheet to Profiles.
  4. For all Google Sheets update nodes (11 total), ensure the same spreadsheet and sheet Feuille 1 are selected and Operation is update.
  5. Credential Required: Connect your googleSheetsOAuth2Api credentials in Fetch Profile Sheet, Append New Profiles, Load Existing Records, and all update nodes (Update Firstname Field, Update Lastname Field, Update Tagline Field, Update Summary Field, Update Experience Field, Update Open Status, Update Hiring Status Field, Update Latest Post).

If you change sheet names, update them consistently across all Google Sheets nodes to prevent silent mismatches.

Step 3: Set Up Profile Retrieval and Filtering

This section pulls fresh profiles from the API, throttles requests, and appends new entries to the sheet.

  1. In Filter Fresh Records, keep the condition where Left Value is ={{ $json.ID }} and the operator is empty.
  2. In Fetch New Posts, set URL to https://api.ghostgenius.fr/v2/profile/posts and add query parameters: url ={{ $json.LinkedIn }} and page 1.
  3. In Delay Step, set Amount to 2 to throttle API calls.
  4. In Retrieve New Profiles, set URL to https://api.ghostgenius.fr/v2/profile and set query parameter url to ={{ $('Filter Fresh Records').item.json.LinkedIn }}.
  5. In Check New Profile Error, keep the condition that checks for ={{ $json.error }} to route errors vs successful results.
  6. Credential Required: Connect your httpHeaderAuth credentials in Fetch New Posts and Retrieve New Profiles.

⚠️ Common Pitfall: If the API requires specific headers, make sure your httpHeaderAuth credential includes them, otherwise the Check New Profile Error branch will fire and no new profiles will be added.

Step 4: Configure Change Detection Logic

After loading existing records, the workflow compares current profile data and routes changes to the correct notification path.

  1. In Fetch Current Posts, set URL to https://api.ghostgenius.fr/v2/profile/posts and query parameters url ={{ $json.LinkedIn }} and page 1.
  2. In Fetch Current Profile, set URL to https://api.ghostgenius.fr/v2/profile with query parameter url ={{ $('Load Existing Records').item.json.LinkedIn }}.
  3. In Change Detection Switch, keep All Matching Outputs enabled and verify each rule compares current fields (e.g., ={{ $json.first_name }}) against sheet fields (e.g., ={{ $('Load Existing Records').item.json.Firstname }}).
  4. In Validate Url Presence, keep the rule that checks ={{ $json.url }} with operator notExists to send unchanged items to No Change Path.
  5. Credential Required: Connect your httpHeaderAuth credentials in Fetch Current Posts and Fetch Current Profile.

The switch can output multiple matches because All Matching Outputs is enabled—this lets you notify on several changes in a single run.

Step 5: Configure Slack Alerts and Sheet Updates

Each detected change sends a Slack alert and then updates the corresponding field in Google Sheets.

  1. Configure Slack messaging nodes with the provided text templates such as Notify First Name using =🚨 First name change detected… and map the expressions exactly as shown.
  2. Repeat for all Slack notification nodes: Notify Last Name, Notify Tagline, Notify Summary, Notify Experience, Notify Open Status, Notify Hiring Status, and Notify New Post.
  3. Ensure each Slack node outputs directly to its matching update node: for example, Notify First Name → Update Firstname Field and Notify New Post → Update Latest Post.
  4. Credential Required: Connect your slackOAuth2Api credentials in all Slack nodes (8 total).

⚠️ Common Pitfall: Don’t forget to replace [YOUR_ID] in each Slack node’s Channel selector, or messages will not be delivered.

Step 6: Test and Activate Your Workflow

Run a manual test to confirm the API calls, change detection, and Slack alerts work end-to-end.

  1. Click Execute Workflow and watch the path from Scheduled Daily Trigger to Fetch Profile Sheet and through the change detection sequence.
  2. Verify that Append New Profiles updates the sheet and that Slack alerts fire for any detected changes.
  3. Confirm that update nodes (e.g., Update Summary Field) write back the latest values to Google Sheets.
  4. Once validated, toggle the workflow to Active so the Scheduled Daily Trigger runs at 8 AM daily.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • Google Sheets credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and confirm the connected Google account still has access to the Sheet.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Slack webhooks can fail if the channel was renamed or the webhook was regenerated. Re-check the incoming webhook URL in Slack, then update the Slack node in n8n.

Next Steps

If your team also needs to expand the list you’re monitoring, Google Sheets to LinkedIn, follows tracked automatically pairs nicely since it helps you operationalize “who we follow” directly from a Sheet.

For teams doing lead enrichment right after a profile change, LinkedIn to Google Sheets, emails filled in for you is a practical add-on so your records don’t stop at a job title.

When outreach happens in LinkedIn messages and you want the same level of tracking you’re building here, LinkedIn to Google Sheets, DMs logged automatically keeps conversation history from getting lost in inbox scroll.

Need better context before you ping someone after a change alert? LinkedIn to Google Sheets, AI summaries ready to use can give your team a short, readable “who is this” snapshot inside the same Sheet.

Finally, if your workflow depends on keeping your Sheet clean across lots of incoming activity (calls, follow-ups, status checks), Calendly + Google Sheets: bookings logged clean helps reduce the messy manual updates that usually creep in.


Quick reference:

Quick Answers

What’s the setup time for this LinkedIn change alerts automation?

About 30 minutes if your Sheet and Slack are ready.

Is coding required for this LinkedIn change alerts automation?

No. You’ll connect accounts, paste an API key, and map a few columns in Google Sheets.

Is n8n free to use for this LinkedIn change alerts workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Ghost Genius API costs based on how many profiles you check.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this LinkedIn change alerts automation for different use cases?

Yes, and you should. You can change the scheduled trigger to weekly (or multiple times per day), then narrow alerts by adjusting the Change Detection Switch paths so only “Latest experience” triggers Slack. Common tweaks include alerting only on job changes, adding an extra Slack mention for VIP profiles, and storing a timestamp column in Google Sheets for each detected update.

Why is my Google Sheets connection failing in this workflow?

Usually it’s an expired Google OAuth connection inside n8n, or the connected account lost access to the Sheet. Re-authenticate the Google Sheets credential and confirm the file is shared with the same Google user. Also check that your sheet columns match what the workflow expects (Firstname, Lastname, LinkedIn URL, ID, and the tracking fields). A renamed tab is another classic “nothing works” cause.

What volume can this LinkedIn change alerts workflow process?

Most small teams comfortably run a few hundred profiles per day as long as you batch requests and respect the scraping API limits.

Is this LinkedIn change alerts automation better than using Zapier or Make?

It depends on how picky you are about change detection. Zapier and Make are fine for simple “new row triggers X,” but this use case needs looping, comparisons, and multiple conditional paths (first name vs. summary vs. job change), and that’s where n8n is simply easier to keep clean. n8n also gives you a self-host option, which matters when the workflow runs daily and you don’t want every check counted as a premium task. If you want Slack messages that include before/after context and a Sheet that stays updated automatically, n8n fits naturally. Talk to an automation expert if you want help choosing.

Once this is running, LinkedIn monitoring becomes a quiet system instead of a recurring chore. The workflow handles the repetitive checks, and you only jump in when there’s something worth acting on.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.