The flow
Starts it 1Logic 5Service 9
The steps in the order they run, from what starts it.
- 1Fare Check TriggerSchedule triggerStarts it
- 2Get Tracked BookingsPostgresService
- 3Prepare Fare SearchCodeLogic
- 4Search Current FaresHttp RequestService
- 5Search Skyscanner FaresHttp RequestService
- 6Analyze Fare DropsCodeLogic
- 7Update Fare TrackingPostgresService
- 8Update Booking StatusPostgresService
- 9Check if Notification NeededIfLogic
- 10Send Fare Drop EmailHttp RequestService
- 11Check if SMS NeededIfLogic
- 12Notify Slack TeamHttp RequestService
- 13Send SMS AlertHttp RequestService
- 14Check Refund EligibleIfLogic
- 15Initiate Refund ProcessHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 15, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Postgres
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Postgres account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 15 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.
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 15 steps before you point it at anything that matters.