JetNetInstall

Overview

This node integrates with the JetNet API, a service providing detailed aviation industry data. Specifically, for the Contact resource and the Get Other Listings operation, it retrieves other company listings associated with a particular contact. This is useful when you want to gather comprehensive information about all companies linked to a contact, such as in customer relationship management or aviation market analysis.

Practical examples:

• Fetching all other companies where a contact holds listings or roles.
• Enriching contact profiles with related company data for sales or marketing purposes.
• Auditing or verifying contact affiliations across multiple companies in the aviation sector.

Properties

Output

The node outputs JSON data representing the other company listings associated with the specified contact. The structure depends on the API response but generally includes details about each related company listing.

• The output is an array of JSON objects, each corresponding to a company listing related to the contact.
• No binary data output is involved in this operation.

Example output snippet (conceptual):

[
  {
    "companyId": "12345",
    "companyName": "Aviation Services Inc.",
    "role": "Owner",
    "listingDetails": { ... }
  },
  {
    "companyId": "67890",
    "companyName": "Global Air Brokers",
    "role": "Broker",
    "listingDetails": { ... }
  }
]

Dependencies

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

Troubleshooting

• Common issues:

  • Invalid or missing Contact ID parameter will cause the API call to fail.
  • Expired or incorrect API authentication token may result in authorization errors.
  • Network connectivity problems can prevent successful API communication.

• Error messages:

  • "Unauthorized" or similar indicates issues with API credentials; verify and update your API key/token.
  • "Not Found" suggests the provided Contact ID does not exist; double-check the ID.
  • Timeout or network errors require checking your internet connection or JetNet service status.

• Resolution tips:

  • Ensure the Contact ID is correct and corresponds to an existing contact in JetNet.
  • Confirm that the API authentication token is valid and has necessary permissions.
  • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

• JetNet Official Website
• JetNet API documentation (access typically requires JetNet account)
• n8n Documentation on HTTP Request Node for understanding underlying request mechanics