Automation library · Customer support

Sync Beex WhatsApp ticket messages with HubSpot

Started by an event in a connected app, and works across HubSpot. 13 steps, 1 branch: a working afternoon to understand properly.

Medium

13 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 9Service 3

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

  1. 1Beex TriggerBeex triggerStarts it
  2. 2Is WhatsApp Channel?FilterLogic
  3. 3Get PhoneSetLogic
  4. 4Search ContactHubspotService
  5. 5Get MessagesBeexService
  6. 6RoutesSwitchLogic
  7. 7Format TextSetLogic
  8. 8Format ImageSetLogic
  9. 9Format AudioSetLogic
  10. 10MergeMergeLogic
  11. 11Sort MessagesSortLogic
  12. 12Consolidate ChatCodeLogic
  13. 13Register ActivityHttp RequestService

How it's built

Starts on
An event in a connected app
Steps
13, with 1 branch
Size
Medium: a working afternoon
Connects to
HubSpot
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own HubSpot 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?

Plan an afternoon. 13 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 13 steps before you point it at anything that matters.