Linkedin Automation
Configured with Airtable, Filter, HTTP Request, Linked In, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Data store
- Code
- Routing
- Messaging
- Trigger
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Get List of records used | Data store | Airtable | search |
| Update the used node | Data store | Airtable | create |
| map used articls ids | Code | Code | See node parameters |
| filter only unused Ids | Routing | Filter | See node parameters |
| get random tags | Code | Code | See node parameters |
| sent the status | Messaging | Telegram | See node parameters |
| Morning 9 Clock | Trigger | Schedule Trigger | See node parameters |
| fetch article ids from tag | Web / API | HTTP Request | See node parameters |
| Fetch Medium post using Article Id | Web / API | HTTP Request | See node parameters |
| If | Routing | If | See node parameters |
| make Linkedin post | Messaging | Linked In | See node parameters |
| Fetch Medium post content | Web / API | HTTP Request | See node parameters |
| download image for post | Web / API | HTTP Request | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
airtableTokenApilinkedInOAuth2ApitelegramApi
Workflow notes
📢 Auto-Post Medium Articles to LinkedIn with Telegram Alerts
📢 Auto-Post Medium Articles to LinkedIn with Telegram Alerts
This n8n workflow automates your LinkedIn posting by fetching articles from medium.com twice a day (9:00 AM and 7:00 PM), ensuring consistent content sharing without manual effort.
To prevent duplicates, it stores posted article IDs in Airtable. It also sends a Telegram message after every successful post, so you stay updated.
✅ Features
✅ Features
- 🕒 Runs twice daily at 9:00 AM and 7:00 PM (customizable)
- 📰 Fetches latest medium.com articles by tag
- 📂 Uses Airtable to avoid reposting the same article
- 📢 Posts to your LinkedIn profile or company page
- 📬 Sends a Telegram notification after successful posting
- ⚙️ Fully customizable schedule, tags, and post format
Linkedin Automation
Linkedin Automation
Purpose and structure
This folder contains the Linkedin Automation workflow. Its executable nodes use airtable, code, filter, httpRequest, if, linkedIn, scheduleTrigger, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Morning 9 Clock
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Linkedin/2024_Linkedin_Telegram_Automate_Webhook.json MIT; preserve source notices.