Actions44
- Contact Actions
- Aircraft Actions
- Get
- Get List
- Get by Registration
- Get Identification
- Get Status
- Get Maintenance
- Get Flights
- Get APU
- Get Avionics
- Get Engine
- Get Airframe
- Get Additional Equipment
- Get Features
- Get Interior
- Get Exterior
- Get Leases
- Get Company Relationships
- Get Pictures
- Get Bulk Aircraft Export Paged
- Get Condensed Owner Operators Paged
- Get Event List Paged
- Get History List Paged
- Company Actions
- Market Actions
Overview
This node integrates with the JetNet API to retrieve detailed aviation industry data related to contacts, aircraft, companies, and market intelligence. Specifically, for the Contact resource and Get Identification operation, it fetches identification details of a specific contact by their unique ID.
Use cases include:
- Retrieving detailed identity information about a contact in the aviation industry.
- Enriching contact records in your workflows with authoritative data from JetNet.
- Automating lookups of contact details for operational or marketing purposes.
Example: Given a contact's unique ID, this node can pull their identification details such as name, title, company affiliation, and other relevant metadata from JetNet.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact whose identification details you want to retrieve. |
Output
The output is a JSON object containing the identification details of the specified contact as returned by the JetNet API. This typically includes fields such as the contact’s name, title, company relationships, and other identifying information.
If multiple items are returned (though unlikely for a single contact ID), each will be output as a separate JSON object.
No binary data is output by this operation.
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 data.
Troubleshooting
- Invalid Contact ID: If the provided contact ID does not exist or is malformed, the API may return an error or empty response. Verify the contact ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the JetNet API endpoint will cause request failures.
- Rate Limits: Excessive requests might be throttled by the API; consider adding delays or retries.
- Error Messages: The node surfaces API error messages. Common errors include "Not Found" for invalid IDs or "Unauthorized" for credential issues.
To resolve errors, check the input parameters, verify credentials, and consult JetNet API documentation or support.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account resources)