Automation library · CRM

Back up Salesforce records to Google Drive CSV

Started by a clock, and works across Gmail, Google Drive and Salesforce. 14 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

14 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
3Services it connects to

The flow

Starts it 1Logic 7Service 6

The steps in the order they run, from what starts it.

  1. 1Daily 02:00Schedule triggerStarts it
  2. 2ConfigSetLogic
  3. 3List Drive folderGoogle DriveService
  4. 4Build ID map + objectsCodeLogic
  5. 5Loop Over ObjectsSplit In BatchesLogic
  6. 6Build summaryCodeLogic
  7. 7Describe objectHttp RequestService
  8. 8Email summaryGmailService
  9. 9Build SOQLCodeLogic
  10. 10Run SOQL querySalesforceService
  11. 11Records -> CSVCodeLogic
  12. 12Have file ID?IfLogic
  13. 13Update fileGoogle DriveService
  14. 14Create fileGoogle DriveService

How it's built

Starts on
A clock
Steps
14, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Gmail, Google Drive, Salesforce
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail, Google Drive and Salesforce 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. 14 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.

Before you run it

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 14 steps before you point it at anything that matters.