Automation library · Alerts and monitoring

Send Slack and email alerts for new Availly bookings

Started by another system calling it, and works across Email. 10 steps, 2 branches: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 5Service 4

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

  1. 1Availly webhookWebhookStarts it
  2. 2Extract raw bodyExtract From FileService
  3. 3Build signed stringSetLogic
  4. 4Compute expected signatureCryptoService
  5. 5Signature valid?IfLogic
  6. 6Parse payloadSetLogic
  7. 7Refuse bad signatureStop And ErrorLogic
  8. 8Not a test ping?IfLogic
  9. 9Post to SlackHttp RequestService
  10. 10Email the ownerEmail SendService

How it's built

Starts on
Another system calling it
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email 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.