Automation library · Integrations

Fetch YouTube channel banner and avatar images

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 8 steps, 2 branches: small enough to read in one sitting and change without fear.

Small

Download free
8 stepsSmall: readable in one sitting
2Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 5Service 2

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

  1. 1When clicking ‘Test workflow’Manual triggerStarts it
  2. 2Set YouTube URLSetLogic
  3. 3Lookup public channel imagesHttp RequestService
  4. 4Lookup succeeded?IfLogic
  5. 5Pick largest banner and avatarCodeLogic
  6. 6Return lookup errorSetLogic
  7. 7Has a public banner?IfLogic
  8. 8Download largest banner JPGHttp RequestService

How it's built

Starts on
An event in a connected app
Steps
8, with 2 branches
Size
Small: readable in one sitting
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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