Automation library · Customer support

Sync contacts and tickets between meiti and HubSpot

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

Medium

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

The flow

Starts it 3Logic 5Service 4

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

  1. 1meiti WebhookWebhookStarts it
  2. 2Has IdentifierIfLogic
  3. 3Search ContactHttp RequestService
  4. 4Respond EmptyRespond To WebhookStarts it
  5. 5Contact FoundIfLogic
  6. 6Resolve ContactSetLogic
  7. 7Create ContactHttp RequestService
  8. 8Search TicketHttp RequestService
  9. 9Ticket FoundIfLogic
  10. 10Resolve TicketSetLogic
  11. 11Create TicketHttp RequestService
  12. 12Respond to meitiRespond To WebhookStarts it

How it's built

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