You don't need to be a developer to build with flight data. If you can drag nodes around in n8n or connect steps in Zapier, you can pull live flight status, decoded weather, or airport details into a spreadsheet, a Slack message, or an email — no code required. The trick is that both tools have a generic "make an HTTP request" action, and an aviation API is just an HTTP request with one header. This guide shows how to wire it up. If you do write code, the flight data API guide for developers covers the same endpoints.
The one thing you need: the base URL and one header
Every SkyLink request is a plain GET to one base URL with one header for authentication. That's the whole contract, and it's all any no-code tool needs:
- Base URL:
https://data.skylinkapi.com/v3.1 - Header
x-api-key: your API key
First, get a key. Your key is issued at checkout and emailed to you; the full walkthrough is in Getting Started. A Free Trial is also available by application, for personal non-commercial use. Keep the key private; both n8n and Zapier let you store it as a saved credential rather than pasting it into every step.

In n8n: the HTTP Request node
n8n has a built-in HTTP Request node that does everything. Add it to your workflow and configure:
- Method:
GET - URL: the endpoint you want, e.g.
https://data.skylinkapi.com/v3.1/flight_status/BA123 - Headers → add one:
x-api-key= your key (store it as an n8n credential and reference it)
- Query parameters (when an endpoint takes them) → add them in the "Query Parameters" section rather than hand-building the URL. For decoded weather, for example, use URL
https://data.skylinkapi.com/v3.1/weather/metar/KJFKwith a query paramparsed=true.
Run the node and n8n returns the JSON response, which every downstream node can read. From there, drop the fields you care about — status, departure.actual_time, arrival.gate — into an Edit Fields node, then into Slack, Google Sheets, or an email node.
In Zapier: Webhooks by Zapier (GET)
Zapier doesn't have a native SkyLink app, but it has a generic Webhooks by Zapier action (available on paid plans) that makes any HTTP request. In your Zap, add an action step and choose Webhooks by Zapier → GET:
- URL:
https://data.skylinkapi.com/v3.1/flight_status/BA123 - Query String Params: add any endpoint parameters as key/value rows (e.g.
parsed=truefor weather). - Headers: add one row,
x-api-key= your key.
Zapier parses the JSON automatically, so the response fields become available as variables you can map into later steps — a Slack message, a row in Google Sheets, an SMS.

A worked example: a flight-status alert with zero code
Here's a complete no-code automation you can build in either tool:
- Trigger — a new row in a Google Sheet containing a flight number (or a schedule/cron trigger that runs every 15 minutes).
- HTTP GET — call
https://data.skylinkapi.com/v3.1/flight_status/{flight_number}with the header, substituting the flight number from the trigger. - Filter — only continue if
statuschanged or the flight is delayed. - Notify — send the
status, gate, and times to Slack or email.
Swap the endpoint and you've got a different tool entirely: /weather/metar/{icao}?parsed=true for an airport weather digest, /airports/search?iata=JFK to enrich a booking row with airport details, or /schedules/departures?icao=EGLL for a daily departures board. The flight status, schedules, and weather endpoints all follow the same request shape.
No-code tips that save headaches
- Store the key as a credential, not inline — both tools support it, and it keeps your key out of shared workflow exports.
- Mind your plan's quota. A workflow that polls every minute burns through a monthly quota fast; schedule triggers at a sensible interval (every 15–30 minutes is plenty for flight status).
- Treat empty strings as "unknown." Fields like gate and terminal come back as
""until the airline publishes them — build your filters around that, not around missing keys. - Test with one record first. Both tools let you run a single step and inspect the raw JSON, so confirm your header is right before switching the automation on.
Plans and quotas are on the pricing page, and the flight operations page lists the flight status and schedule endpoints used above.

