n8n Integration, Automate LinkedIn Workflows with OutX

​

What You Can Build

​

Prerequisites

• An OutX account with an API key (get your key)
• The OutX Chrome extension installed and active
• An n8n instance (cloud or self-hosted)

​

Step-by-Step: LinkedIn Posts → Slack Alerts

​

1. Schedule Trigger

​

2. Fetch Posts (HTTP Request)

• Method: GET
• URL: https://api.outx.ai/api-posts
• Authentication: Header Auth
  • Name: x-api-key
  • Value: {{ $env.OUTX_API_KEY }}
• Query Parameters:
  • watchlist_id: your watchlist ID
  • sort_by: recent_first
  • page: 1

​

3. Filter New Posts (Code Node)

// Store seen post IDs in static data
const seen = $getWorkflowStaticData("global");
if (!seen.postIds) seen.postIds = [];

const newPosts = $input.all().filter(item => {
  const postId = item.json.data?.id || item.json.id;
  if (seen.postIds.includes(postId)) return false;
  seen.postIds.push(postId);
  return true;
});

// Keep only last 500 IDs to avoid memory issues
if (seen.postIds.length > 500) {
  seen.postIds = seen.postIds.slice(-500);
}

return newPosts;

​

4. Send to Slack

• Channel: #linkedin-alerts
• Message:

New LinkedIn post by {{ $json.author_name }}:
{{ $json.content.substring(0, 300) }}

Post URL: {{ $json.post_url }}
Engagement: {{ $json.likes_count }} likes, {{ $json.comments_count }} comments

​

Step-by-Step: Fetch Profile → Google Sheets

​

1. Create the Task (HTTP Request)

{
  "method": "POST",
  "url": "https://api.outx.ai/linkedin-agent/fetch-profile",
  "headers": {
    "x-api-key": "{{ $env.OUTX_API_KEY }}",
    "Content-Type": "application/json"
  },
  "body": {
    "profile_slug": "{{ $json.slug }}"
  }
}

​

2. Wait for Completion

GET https://api.outx.ai/linkedin-agent/get-task-status?api_agent_task_id={{ $json.api_agent_task_id }}

• completed → continue to Google Sheets
• pending or processing → loop back to Wait

​

3. Write to Google Sheets

​

Tips

• Use environment variables for your API key, never hardcode it in n8n nodes
• Add error handling with an Error Trigger node to catch failed HTTP requests
• Rate limit LinkedIn Data API calls, add Wait nodes (30–60s) between consecutive requests
• Use n8n’s static data to track which posts you’ve already processed

​

Related

• API Quick Start, Watchlists & Engagement API basics
• LinkedIn Data Quick Start, Fetch profiles and posts
• Rate Limits, Safe usage guidelines
• Use Cases, Common API workflows

​

Partnerships

​

Learn More

• LinkedIn API Guide
• LinkedIn Slack Integration