The flow
Starts it 1Logic 3Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get All ContentDocuments older than 365 days agoSalesforceService
- 3Loop Over Each File RecordSplit In BatchesLogic
- 4Send Slack NotificationSlackService
- 5Download File ContentHttp RequestService
- 6Upload to S3Aws S3Service
- 7Get LinkedEntityId from ContentDocumentLinkSalesforceService
- 8Filter Out User AttachmentsCodeLogic
- 9Create S3_File__c RecordSalesforceService
- 10Prepare ContentDocumentId for DeletionCodeLogic
- 11Delete Original File in SalesforceHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 11, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- S3, Salesforce, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own S3, Salesforce and Slack accounts. 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. 11 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 11 steps before you point it at anything that matters.