JetNet icon

JetNet

Interact with JetNet API for aviation industry data

Overview

This node integrates with the JetNet API to retrieve aviation industry data related to aircraft, companies, contacts, and market intelligence. Specifically, for the Aircraft resource and the Get Event List Paged operation, it fetches a paginated list of events associated with aircraft. This is useful for users who want to analyze or monitor aircraft event histories in manageable chunks rather than retrieving all data at once.

Typical use cases include:

  • Monitoring recent or historical events related to specific aircraft.
  • Integrating aircraft event data into aviation management systems.
  • Performing audits or compliance checks based on event logs.
  • Building dashboards that display aircraft event information page by page.

Example: Retrieve 50 aircraft events per page and process them sequentially to build a timeline of maintenance or operational events.

Properties

Name Meaning
Page Size Number of results to retrieve per page (minimum 1, maximum 1000).
Page The page number to retrieve (starting from 1).

These properties control pagination of the aircraft event list, allowing users to specify how many events to get per request and which page of results to access.

Output

The node outputs JSON data representing the aircraft event list for the requested page. The structure corresponds directly to the response from the JetNet API's /api/Aircraft/getEventListPaged endpoint.

  • If multiple events are returned, each event is output as a separate JSON item.
  • Each event object contains details about an individual aircraft event (e.g., event type, date, description).
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the JetNet API via an API key credential configured in n8n.
  • The base URL for requests is https://customer.jetnetconnect.com.
  • Proper API authentication token must be provided through credentials.
  • Network connectivity to the JetNet service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause authorization errors.
    • Requesting a page number beyond available pages may return empty results.
    • Providing a page size outside the allowed range (less than 1 or greater than 1000) may cause validation errors.
    • Network timeouts or connectivity problems can interrupt data retrieval.
  • Error messages:

    • Authorization errors typically indicate invalid credentials; verify API key setup.
    • Validation errors on parameters suggest adjusting "Page Size" and "Page" inputs within allowed ranges.
    • Unexpected API errors should be checked against JetNet API status or contact support.
  • To handle errors gracefully, enable the node’s "Continue On Fail" option to allow workflow execution to proceed despite individual request failures.

Links and References


If you need summaries for other resources or operations, feel free to ask!

Discussion