Automation library · Integrations

Automated Zalo OA token management with OAuth

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

Medium

9 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 3Logic 5Service 1

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Execute_NodeWebhookStarts it
  3. 3WebhookWebhookStarts it
  4. 4Set Refresh Token and App IDSetLogic
  5. 5Clean Zalo Static DataCodeLogic
  6. 6Load Access TokenCodeLogic
  7. 7Load to Static DataCodeLogic
  8. 8Refresh Token (Zalo v4)Http RequestService
  9. 9Store to SD & Pass tokenCodeLogic

How it's built

Starts on
Another system calling it
Steps
9
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. 9 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 9 steps before you point it at anything that matters.