The flow
Starts it 2Logic 3Service 7
The steps in the order they run, from what starts it.
- 1Manual Trigger - Test RunManual triggerStarts it
- 2Cron - Every 5 MinutesSchedule triggerStarts it
- 3Fetch Scheduled Posts (Twenty CRM)PostgresService
- 4Process Posts (Split in Batches)Split In BatchesLogic
- 5Check Attachment Present?IfLogic
- 6Build SharePoint ShareIdCodeLogic
- 7Unipile - Create Post (Text Only)Http RequestService
- 8SharePoint - Resolve Drive ItemHttp RequestService
- 9Unipile - Get Post DetailsHttp RequestService
- 10SharePoint - Download Attachment (Binary)Http RequestService
- 11Mark Post as POSTED (Twenty CRM Update)PostgresService
- 12Unipile - Create Post (With Attachment)Http RequestService
How it's built
- Starts on
- A clock
- Steps
- 12, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Postgres
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Postgres account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 12 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.