# Sync data between Google Drive and AWS S3: n8n workflow

> Started by an event in a connected app, and works across S3. 4 steps: small enough to read in one sitting and change without fear.

Source: https://millionrounds.com/workflow/sync-data-between-google-drive-and-aws-s3 (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Data collection](https://millionrounds.com/workflows?category=Data+collection#library)

# Sync data between Google Drive and AWS S3

Started by an event in a connected app, and works across S3. 4 steps: small enough to read in one sitting and change without fear.

Small

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fsync-data-between-google-drive-and-aws-s3)

**4 steps** Small: readable in one sitting

**0** Branches: places the flow splits

**0** Loops or waits

**1** Service it connects to

## The flow

Starts it 1 Logic 1 Service 2

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

- 1 **Google Drive Trigger** Google Drive trigger *Starts it*
- 2 **AWS S3 - get** Aws S3 *Service*
- 3 **Merge** Merge *Logic*
- 4 **AWS S3 - upload** Aws S3 *Service*

## How it's built

- **Starts on:** An event in a connected app
- **Steps:** 4
- **Size:** Small: readable in one sitting
- **Connects to:** S3
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account, plus your own S3 account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

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?

Not long. At 4 steps it can be read in one sitting and changed without fear.

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

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fsync-data-between-google-drive-and-aws-s3)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[S3](https://millionrounds.com/workflows?service=S3#library)

## Workflows like it

Also data collection, with the same services where possible, closest in size first.

- [**Extract and store text from chat images with AWS S3** 4 steps · Airtable, S3](https://millionrounds.com/workflow/extract-and-store-text-from-chat-images-with-aws-s3)
- [**Sync OpenAI vector stores from Google Sheets with Drive** 19 steps · calls a model · Google Drive, Google Sheets](https://millionrounds.com/workflow/sync-openai-vector-stores-from-google-sheets-with-drive)
- [**Automate viral video generation with Shotstack, OpenAI, and S3** 30 steps · calls a model · S3, Supabase](https://millionrounds.com/workflow/automacao-gerar-videos-virais-shotstack-with-openai-and-s3)