JetNetInstall

Overview

This node integrates with the JetNet API to retrieve aviation industry data related to contacts, specifically focusing on aircraft relationships associated with a contact. The "Get Aircraft Relationships" operation under the "Contact" resource fetches all aircraft relationships linked to a specified contact by their unique Contact ID.

Typical use cases include:

• Fetching all aircraft that a particular contact is related to, such as owner, operator, or broker relationships.
• Integrating contact-aircraft relationship data into workflows for aviation management, CRM enrichment, or reporting.
• Automating updates or notifications based on changes in aircraft relationships for specific contacts.

Example: Given a Contact ID, the node can retrieve all aircraft connected to that contact, enabling further processing or analysis within an n8n workflow.

Properties

Output

The node outputs JSON data representing the aircraft relationships for the specified contact. The structure typically includes details about each aircraft related to the contact, such as identifiers and relationship types. The output is an array of objects if multiple relationships exist.

No binary data output is involved in this operation.

Example output snippet (conceptual):

[
  {
    "aircraftId": "12345",
    "relationshipType": "Owner",
    "aircraftDetails": { ... }
  },
  {
    "aircraftId": "67890",
    "relationshipType": "Operator",
    "aircraftDetails": { ... }
  }
]

Dependencies

• Requires an active connection to the JetNet API.
• An API authentication token credential must be configured in n8n to authorize requests.
• The node sends HTTP GET requests to the endpoint /api/Contact/getContAircraftRelationships/{contactId}/{apiToken}.

Troubleshooting

• Common issues:

  • Invalid or missing Contact ID: The API will fail to return data if the Contact ID is incorrect or not provided.
  • Authentication errors: Ensure the API key credential is valid and has necessary permissions.
  • Network connectivity problems may cause request failures.

• Error messages:

  • Errors from the API are caught and returned as error messages in the node output if "Continue On Fail" is enabled.
  • Typical error messages might include "Contact not found" or "Unauthorized access".

• Resolution tips:

  • Verify the Contact ID is correct and exists in the JetNet system.
  • Check API credentials and refresh if expired.
  • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

• JetNet API Documentation (login required)
• n8n documentation on HTTP Request Node for understanding underlying HTTP calls
• Aviation industry data integration best practices (general reference)