See llms.txt for all machine-readable content.

Back to Templates

Send real-time flight change alerts with FlightByte, Slack, email, and SMS

Created by

Created by: Batuhan ERKAN || flightbyte
Batuhan ERKAN

Last update

Last update 4 hours ago

Categories

Quick overview

This workflow lets users submit flights to FlightByte for monitoring and then delivers verified flight change events to Slack, with optional SendGrid email and Twilio SMS alerts, while storing passenger contact details in an n8n Data Table.

How it works

  1. Receives flight details via an n8n Form trigger and creates (or reuses) the flightbyte_passengers n8n Data Table.
  2. Sends the flight details and the workflow’s webhook URL to the FlightByte API to create a subscription, then stores the returned subscription ID with the passenger’s contact info.
  3. Receives FlightByte change events on a webhook, validates the HMAC signature and timestamp, and immediately responds with HTTP 204 to stop retries.
  4. Deduplicates events already handled in previous executions and routes the payload by event type (flight update, test, suspended, or completed).
  5. For flight update events, looks up the passenger contact row, formats a Slack message, and posts it to Slack.
  6. For flight update events, sends an email via SendGrid for selected change types (such as gate, time, delay, cancellation, and diversion) and sends an SMS via Twilio for cancellations/diversions or arrival delays of 60 minutes or more.
  7. For completed subscriptions, deletes the passenger row from the n8n Data Table, and for test/suspended events, posts a notification to Slack.

Setup

  1. Create a FlightByte API key and add an HTTP Custom Auth credential for the FlightByte request, including an x-api-key header and a shared webhook signing secret in the request body.
  2. Add a Crypto credential with the same HMAC secret so the workflow can verify FlightByte webhook signatures.
  3. Add Slack credentials and select the target channel in each Slack message step.
  4. Add SendGrid credentials and set the “from” email/name used to send passenger alerts.
  5. Add Twilio credentials and set the Twilio “from” phone number used to send SMS alerts.

Requirements

  • n8n 2.x reachable over public HTTPS. n8n Cloud works as is; a self-hosted n8n needs WEBHOOK_URL set to its public address.
  • A FlightByte API key. The Free plan covers three watched flights a month.
  • Slack, SendGrid and Twilio credentials. Delete the channels you don’t use.

Customization

  • Edit EMAIL_CHANGES and SMS_DELAY_MINUTES at the top of Write the messages to change who hears about what.
  • Swap the form for Google Sheets, Airtable or your booking system, and map its columns in Build the request.
  • Replace Slack with Microsoft Teams, Discord or Telegram, and SendGrid with Gmail or SMTP.
  • Add an events filter in Watch the flight so FlightByte only sends the change types you need.

Additional info

Built only from n8n's built-in nodes and tested on n8n 2.44, including a live delivery from FlightByte. Passenger contact details stay in an n8n data table and are deleted when the flight completes; FlightByte only receives the flight and the booking reference.

Step-by-step guide: https://flightbyte.dev/guides/flight-change-alerts-n8n?utm_source=n8n&utm_medium=listing&utm_campaign=flight-change-alerts