See llms.txt for all machine-readable content.

Back to Templates

Publish scheduled LinkedIn posts from Twenty CRM via Unipile and SharePoint

Created by

Created by: Swapnil Mandloi || swapnil-mandloi
Swapnil Mandloi

Last update

Last update 18 hours ago

Categories

Share

Quick overview

Automate your LinkedIn content calendar. This workflow fetches scheduled posts from a PostgreSQL database (Twenty CRM), downloads attached media from SharePoint, and publishes them seamlessly to LinkedIn using Unipile.

How it works

  1. A Schedule Trigger (Cron) fires every 5 minutes to check for pending social media posts
  2. A PostgreSQL node queries the database to fetch posts marked as 'SCHEDULED' where the scheduled time has passed.
  3. A Split In Batches node loops through the fetched posts one by one to prevent API concurrency issues.
  4. An IF node checks if there is a SharePoint attachment URL included in the database record.
  5. If an attachment exists, Microsoft Graph API nodes resolve the SharePoint Drive Item and download the image as a binary file
  6. HTTP Request nodes send the text (and binary attachment, if any) to Unipile's API to natively publish the LinkedIn post.
  7. A final PostgreSQL node updates the CRM record to 'POSTED' and saves the live LinkedIn post URL back to the database.

Setup

  1. Add your PostgreSQL credentials and verify that the SQL query matches your Twenty CRM table and schema names.
  2. Connect your Microsoft Entra ID (Azure AD) account to authenticate SharePoint access.
  3. Configure the HTTP Request nodes with your Unipile Account ID and API keys via HTTP Header Auth.
  4. Activate the workflow to allow the 5-minute cron trigger to run continuously in the background.

Requirements

  • PostgreSQL database (Twenty CRM) , Unipile Account (with an active LinkedIn session),Microsoft Entra ID / SharePoint Account

Customization

  • Adjust the LIMIT 10 in the initial SQL query if you want to process more or fewer posts per batch.Replace the SharePoint nodes with Google Drive or AWS S3 nodes if you store your post attachments elsewhere.