What You Can Build
| Workflow | OutX API | n8n Nodes |
|---|---|---|
| New LinkedIn post → Slack alert | GET /api-posts | Schedule Trigger → HTTP Request → Slack |
| Buying intent detected → CRM lead | GET /api-posts + filters | Schedule Trigger → HTTP Request → HubSpot/Salesforce |
| New post → AI comment → post comment | GET /api-posts → OpenAI → POST /api-comment | Schedule Trigger → HTTP Request → OpenAI → HTTP Request |
| Profile fetch → lead enrichment | POST /linkedin-agent/fetch-profile → poll | HTTP Request → Wait → HTTP Request → Google Sheets |
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
This workflow checks your watchlist every hour and sends new posts to Slack.1. Schedule Trigger
Add a Schedule Trigger node. Set it to run every 60 minutes.2. Fetch Posts (HTTP Request)
Add an HTTP Request node:- Method: GET
- URL:
https://api.outx.ai/api-posts - Authentication: Header Auth
- Name:
x-api-key - Value:
{{ $env.OUTX_API_KEY }}
- Name:
- Query Parameters:
watchlist_id: your watchlist IDsort_by:recent_firstpage:1
3. Filter New Posts (Code Node)
Add a Code node to filter posts you haven’t seen:4. Send to Slack
Add a Slack node:- Channel:
#linkedin-alerts - Message:
Step-by-Step: Fetch Profile → Google Sheets
This workflow fetches a LinkedIn profile and adds the data to a Google Sheet.1. Create the Task (HTTP Request)
2. Wait for Completion
Add a Wait node set to 10 seconds, then an HTTP Request node to poll:{{ $json.data.status }}:
completed→ continue to Google Sheetspendingorprocessing→ loop back to Wait
3. Write to Google Sheets
Map the profile fields:| Sheet Column | n8n Expression |
|---|---|
| Name | {{ $json.data.task_output.profile.full_name }} |
| Headline | {{ $json.data.task_output.profile.headline }} |
| Location | {{ $json.data.task_output.profile.location }} |
| LinkedIn URL | https://linkedin.com/in/{{ $json.data.task_output.profile.profile_slug }} |
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

