Monitor Dev.to, post new articles to LinkedIn twice daily, track with Airtable, and alert via Telegram.
Fetches the latest Dev.to articles by tag and queues them for publishing. Checks Airtable to filter duplicates and ensure only unseen articles are posted. Posts to LinkedIn twice daily and sends a Telegram alert after each successful post.
Executes the end-to-end posting flow and keeps content fresh and tracked.
Fetches Dev.to articles by tag.
Checks Airtable for existing ArticleIDs to prevent duplicates.
Parses article data into a LinkedIn-ready post.
Posts new articles to LinkedIn according to schedule.
Saves new ArticleID to Airtable for future checks.
Sends Telegram alerts after successful posts.
Before the AI agent, manual posting consumed time and risked missed opportunities. After adoption, you have a reliable schedule with automated deduplication, status updates, and real-time alerts.
A simple 3-step flow that's easy to follow.
The AI agent queries the Dev.to API using your chosen tag to retrieve the latest articles.
The AI agent searches Airtable for ArticleID; if not found, it prepares a LinkedIn post payload.
Publish the post to LinkedIn, save the new ArticleID in Airtable, and send a Telegram alert.
A realistic run showing times, actions, and results.
Scenario: At 9:00 AM, the AI agent triggers via the scheduler and fetches Dev.to articles tagged 'ai'. It identifies a new article with ID 98765 and formats a LinkedIn post. The post goes live on the user’s profile, ArticleID 98765 is saved to Airtable, and a Telegram alert is sent confirming the publish. The next post occurs at 7:00 PM following the same flow, ensuring a consistent LinkedIn presence.
Roles that gain from automated Dev.to to LinkedIn posting.
Need a consistent LinkedIn presence to build a personal brand with minimal manual effort.
Want to repurpose Dev.to content for LinkedIn without duplicating work.
Regularly share technical insights and tutorials to a broader audience.
Maintain a steady stream of posts for pages and groups.
Automate content distribution and track performance with auditable logs.
Scale posting without sacrificing quality or oversight.
Tools used to run the AI agent and how they interact.
Stores ArticleID and checks for duplicates to prevent reposts.
Fetches the latest articles by tag for posting.
Posts content to a user profile or company page.
Sends a notification after a successful LinkedIn post.
Triggers the workflow twice daily at 9:00 AM and 7:00 PM.
Common scenarios where this AI agent adds value.
Common questions and practical answers.
Yes. The agent posts Dev.to articles to LinkedIn on a set schedule. It checks for duplicates before posting and logs each action in Airtable. After posting, a Telegram alert confirms success. You can modify the posting times and the content format to suit your style and compliance needs. If LinkedIn blocks automated posts, you can pause or adjust the schedule without losing data because Airtable maintains a complete post history.
Absolutely. You can set the Dev.to tag used for fetching articles and adjust the 9:00 AM and 7:00 PM times. The LinkedIn post format can include hashtags, emojis, and your personal notes. The frequency can be changed, and you can add additional filters (e.g., minimum word count or presence of a cover image). Changes apply to future posts while preserving existing Airtable records for auditability.
Airtable stores each ArticleID after a successful post. Before posting, the AI agent searches Airtable for that ID. If it exists, the article is skipped; if not, the agent proceeds to craft and publish the LinkedIn post and then logs the new ID. This ensures no article is reposted unintentionally. The Airtable table acts as a single source of truth for duplicates.
Both options are supported. You can connect either a user profile or a company page via LinkedIn’s API, and the AI agent will publish to the selected destination. Access controls and OAuth settings determine who can authorize changes to the posting configuration. If you switch targets, you may need to adjust permissions and the post formatting accordingly. The action history remains auditable in Airtable.
The AI agent handles API errors with retry logic and clear alerts. If authentication fails, the system surfaces the issue via Telegram and logs an error in the tracking base. Retries use exponential backoff to avoid hammering the API. If the tag fetch repeatedly fails, the agent pauses posting and notifies the administrator for manual intervention.
Yes. The solution uses standard OAuth2 authentication for LinkedIn and stores references to ArticleIDs in Airtable. It adheres to typical automation best practices and keeps credentials out of content payloads. You should still monitor for any policy changes from LinkedIn and adjust the scope of permissions if necessary. Regular audits of the Airtable logs help ensure data integrity and compliance.
Yes. The AI agent’s workflow can be paused and resumed without losing historical data in Airtable. When paused, no new posts are generated, but existing ArticleIDs remain tracked. Resuming reactivates the schedule and continues duplicate checks from the current Airtable state. This allows you to control campaigns around launches, holidays, or team availability.
Monitor Dev.to, post new articles to LinkedIn twice daily, track with Airtable, and alert via Telegram.
