Automation library · Documents and files

Extract structured data from medical documents with Gemini

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 10 steps: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 4Service 4

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

  1. 1Webhook InputWebhookStarts it
  2. 2Parse InputSetLogic
  3. 3Download ImageHttp RequestService
  4. 4Extract to Base64Extract From FileService
  5. 5Prepare for AISetLogic
  6. 6Gemini Classify ExtractHttp RequestService
  7. 7Parse AI ResultsSetLogic
  8. 8Gemini Structure DataHttp RequestService
  9. 9Finalize TrackSetLogic
  10. 10API ResponseRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
10
Size
Medium: a working afternoon
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 another system calling it.

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