LinkedIn company posts to Slack with n8n

Method

1. Get an Apify token

   Sign in to Apify and copy a personal API token from Console: Settings, API and integrations. The workflow keeps it in an n8n credential, never in the file.

2. Import the workflow

   In n8n choose Workflows, Import from file, or paste the JSON onto an empty canvas.

   • Run by hand
   • Every day
   • Run Apify Actor
   • Only records not sent before
   • Send to Slack

   n8n workflowlinkedin-company-posts-to-slack.n8n.json

   Copy Download Actor on Apify

   Show the file (172 lines)

   {
     "name": "LinkedIn company posts to Slack",
     "nodes": [
       {
         "id": "e8855516-a44a-4401-ae4d-dd30d7f5f11b",
         "name": "Run by hand",
         "type": "n8n-nodes-base.manualTrigger",
         "typeVersion": 1,
         "position": [
           0,
           0
         ],
         "parameters": {}
       },
       {
         "id": "77e28396-aee6-4877-a3dc-7ba6fc853a2b",
         "name": "Every day",
         "type": "n8n-nodes-base.scheduleTrigger",
         "typeVersion": 1.2,
         "position": [
           0,
           200
         ],
         "parameters": {
           "rule": {
             "interval": [
               {
                 "triggerAtHour": 8
               }
             ]
           }
         },
         "notes": "Activate the workflow to run on this schedule."
       },
       {
         "id": "93a313aa-1270-43d0-ac71-bb1d98e93c4b",
         "name": "Run Apify Actor",
         "type": "n8n-nodes-base.httpRequest",
         "typeVersion": 4.2,
         "position": [
           260,
           100
         ],
         "parameters": {
           "method": "POST",
           "url": "https://api.apify.com/v2/actors/vexaloom-labs~linkedin-company-page-post-and-engagement/run-sync-get-dataset-items",
           "authentication": "genericCredentialType",
           "genericAuthType": "httpHeaderAuth",
           "sendBody": true,
           "specifyBody": "json",
           "jsonBody": "{\n  \"mode\": \"auto\",\n  \"companyUrls\": [\n    \"https://www.linkedin.com/company/hubspot/\"\n  ],\n  \"maxPostsPerCompany\": 5,\n  \"includeEmployeePosts\": false,\n  \"includeIndexedPosts\": false,\n  \"minReactions\": 0,\n  \"minComments\": 0,\n  \"sortBy\": \"recent\",\n  \"includeReposts\": true,\n  \"hydratePosts\": true,\n  \"includeReactionBreakdown\": false,\n  \"includeDocumentDetails\": false,\n  \"monitorMode\": true,\n  \"language\": \"en\"\n}",
           "options": {
             "timeout": 310000
           }
         },
         "notes": "Actor: vexaloom-labs/linkedin-company-page-post-and-engagement. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
         "notesInFlow": false
       },
       {
         "id": "9d5d5cf6-b341-4715-a9a7-3c6cd0cc313b",
         "name": "Only records not sent before",
         "type": "n8n-nodes-base.removeDuplicates",
         "typeVersion": 2,
         "position": [
           500,
           100
         ],
         "parameters": {
           "operation": "removeItemsSeenInPreviousExecutions",
           "logic": "removeItemsWithAlreadySeenKeyValues",
           "dedupeValue": "={{ $json.postUrl }}",
           "options": {
             "scope": "node",
             "historySize": 10000
           }
         },
         "notes": "Remembers each postUrl it has passed on (up to 10,000) across runs, so a record is sent once. Needs n8n 1.64 or later."
       },
       {
         "id": "feb9ddde-2c05-4d43-a6e1-248ea56ebdf3",
         "name": "Send to Slack",
         "type": "n8n-nodes-base.slack",
         "typeVersion": 2.3,
         "position": [
           740,
           100
         ],
         "parameters": {
           "select": "channel",
           "channelId": {
             "__rl": true,
             "value": "",
             "mode": "list"
           },
           "text": "={{ [$json.companyName, $json.text, $json.reactionsCount, $json.commentsCount, $json.postUrl].filter(v => v !== undefined && v !== null && v !== '').join(' | ') }}",
           "otherOptions": {}
         },
         "notes": "Pick your Slack credential and channel."
       },
       {
         "id": "e41da4e6-177a-4bb7-a586-c1c2c20bed2b",
         "name": "Setup",
         "type": "n8n-nodes-base.stickyNote",
         "typeVersion": 1,
         "position": [
           0,
           -370
         ],
         "parameters": {
           "content": "## LinkedIn Company Page Post & Engagement Extractor\n\nSource: [vexaloom-labs/linkedin-company-page-post-and-engagement](https://apify.com/vexaloom-labs/linkedin-company-page-post-and-engagement) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Open **Send to Slack** and connect your Slack account.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
           "height": 340,
           "width": 460,
           "color": 6
         }
       }
     ],
     "connections": {
       "Run by hand": {
         "main": [
           [
             {
               "node": "Run Apify Actor",
               "type": "main",
               "index": 0
             }
           ]
         ]
       },
       "Every day": {
         "main": [
           [
             {
               "node": "Run Apify Actor",
               "type": "main",
               "index": 0
             }
           ]
         ]
       },
       "Run Apify Actor": {
         "main": [
           [
             {
               "node": "Only records not sent before",
               "type": "main",
               "index": 0
             }
           ]
         ]
       },
       "Only records not sent before": {
         "main": [
           [
             {
               "node": "Send to Slack",
               "type": "main",
               "index": 0
             }
           ]
         ]
       }
     },
     "pinData": {},
     "active": false,
     "settings": {
       "executionOrder": "v1"
     },
     "meta": {
       "templateCredsSetupCompleted": false
     },
     "tags": []
   }

   Validated, not executed: 11 of 11 checks pass

   • It has a nodes array and a connections object
   • Every node has a name, type, typeVersion, position and parameters
   • Node names are unique
   • Every node type is a known n8n core node (or the Apify node)
   • Every node uses a typeVersion that n8n ships
   • Every connection points at an existing node
   • At least one trigger starts the workflow
   • Every working node is reachable from a trigger
   • Apify calls use POST and a credential for the token
   • Actor input matches the Actor's published input schema
   • No token or credential value is embedded

3. Add the Apify credential

   Open Run Apify Actor. Under Credential, create a Header Auth credential with the name Authorization and the value Bearer, a space and your token.

4. Set the input

   The request body holds the Actor input: the Actor's Store prefill with companyUrls, maxPostsPerCompany, monitorMode set for this recipe. Change companyUrls and maxPostsPerCompany to your own.

   {
     "mode": "auto",
     "companyUrls": [
       "https://www.linkedin.com/company/hubspot/"
     ],
     "maxPostsPerCompany": 5,
     "includeEmployeePosts": false,
     "includeIndexedPosts": false,
     "minReactions": 0,
     "minComments": 0,
     "sortBy": "recent",
     "includeReposts": true,
     "hydratePosts": true,
     "includeReactionBreakdown": false,
     "includeDocumentDetails": false,
     "monitorMode": true,
     "language": "en"
   }

   Every input field is documented on the LinkedIn Company Page Post & Engagement Extractor page.

5. Only new records go through

   The Only records not sent before node (n8n's Remove Duplicates, set to remove items processed in previous executions) remembers each postUrl it has passed on, so a record reaches Slack once even when the next run returns it again. It needs n8n 1.64 or later; clear its history from the node to resend everything.

6. Connect Slack

   Open Send to Slack, select your Slack credential and pick the channel. Each message shows companyName, text, reactionsCount, commentsCount, postUrl.

7. Run once, then turn it on

   Click Execute workflow and check the first records in Slack. When they look right, activate the workflow so the daily trigger runs it at 08:00 in your instance's timezone.

Where it breaks

• Reaction and comment counts are the numbers at the moment of the run; a post that takes off later is not re-sent with new counts.
• Only public company page posts are read. Posts by employees stay out unless you switch on includeEmployeePosts.
• Long posts arrive in full, so a busy page can make long Slack messages; lower maxPostsPerCompany if the channel gets noisy.
• The workflow uses Apify's synchronous endpoint, which waits up to 300 seconds. Bigger runs answer HTTP 408: lower the limit or switch to an asynchronous run.
• Each run is billed to your Apify account at the Store price ($0.99 per 1,000 results (pay per event)).

Bigger runs: the long-run workflow starts the run, waits for it and reads the dataset, so it never hits the 300-second limit.

If the workflow fails

Why does the workflow or script stop with HTTP 408?

The synchronous endpoint waits at most 300 seconds. After that it answers 408 while the run keeps going in Apify. Lower the result limit, or start the run asynchronously, wait for it to finish and then read its dataset.

Source: Apify API: run Actor synchronously and get dataset items

What do 400, 401, 402 and 403 from the Apify API mean?

Read error.type in the response body. 400 is invalid Actor input. 401 (user-or-token-not-found) means a token reached Apify but it is wrong or revoked. 402 with x402-payment-required means no token reached Apify at all: the n8n credential or the Authorization: Bearer header is missing, and Apify is offering its pay-per-run x402 route for agents instead; any other 402 is an exhausted usage limit on the account that pays for the run. 403 is a token without permission for that Actor or storage.

Source: Apify API: authentication; Apify documentation: agentic payments with x402; Apify API: run Actor synchronously and get dataset items

n8n says Install this node to use it after import. Why?

The workflow names a node or node version your instance does not have, usually a community node. The workflows here use only built-in nodes at versions n8n has shipped since 1.80, so they import on n8n Cloud and older self-hosted instances without community nodes.

Source: n8n issue: unrecognized node type after import

Why does the HTTP Request node time out before Apify answers?

Set the node's Timeout option to at least 300000 ms so n8n waits as long as Apify's synchronous endpoint. The workflows here already set 310000. A failure at exactly 30 seconds points to a proxy in front of n8n.

Source: n8n HTTP Request node documentation

Every fix in one place

Same data in an agent

Want Claude, Cursor or ChatGPT to call the Actor directly instead of on a schedule? The LinkedIn Company Page Post & Engagement Extractor page has MCP configs for eight clients and a SKILL.md. The LinkedIn MCP server bundles every LinkedIn Actor in one URL.