JetNet icon

JetNet

Interact with JetNet API for aviation industry data

Overview

This node integrates with the JetNet API to retrieve detailed aviation industry data related to aircraft, companies, contacts, and market intelligence. Specifically, for the Aircraft resource and the Get Leases operation, it fetches lease information associated with a particular aircraft identified by its unique Aircraft ID.

This node is beneficial in scenarios where users need to access comprehensive leasing details of an aircraft, such as lease terms, lessors, lessees, and lease history. Practical examples include aviation asset management, financial analysis of aircraft leases, or integration into maintenance and operational workflows that require lease status verification.

Properties

Name Meaning
Aircraft ID The unique identifier of the aircraft for which lease information is requested.

Output

The output contains JSON data representing the lease information of the specified aircraft. This typically includes details such as lease agreements, parties involved (lessor and lessee), lease durations, and other relevant lease metadata provided by the JetNet API.

If multiple lease records exist, the output will be an array of JSON objects, each corresponding to a lease entry. If no leases are found, the output may be an empty object or array.

The node does not output binary data.

Dependencies

  • Requires an active connection to the JetNet API.
  • Requires an API authentication token credential configured in n8n to authorize requests.
  • The base URL for API requests is https://customer.jetnetconnect.com.
  • The node uses HTTP GET requests to fetch lease data for the given Aircraft ID.

Troubleshooting

  • Common Issues:

    • Invalid or missing Aircraft ID: Ensure the Aircraft ID is correctly provided and corresponds to an existing aircraft in JetNet.
    • Authentication errors: Verify that the API key or token credential is valid and has sufficient permissions.
    • Network connectivity issues: Confirm that the n8n instance can reach the JetNet API endpoint.
  • Error Messages:

    • Errors returned from the API (e.g., 404 Not Found) usually indicate the Aircraft ID does not exist or is inaccessible.
    • Authentication failures will result in authorization errors; recheck credentials.
    • Timeout or network errors suggest connectivity problems; retry or check network settings.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to allow workflow continuation despite individual request failures.

Links and References

Discussion