Actions68
- 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
- Get Bulk Aircraft Export Paged
- Get Condensed Snapshot
- Get Condensed Owner Operators
- Get Condensed Owner Operators Paged
- Get Event List
- Get Event List Paged
- Get History List
- Get History List Paged
- Get Flight Data
- Get Relationships
- Company Actions
- Contact Actions
- Market Actions
- Get Model Intelligence
- Get Model Market Trends
- Get Model Operation Costs
- Get Model Performance Specs
- Get Account Info
- Get Product Codes
- Get Airframe Types
- Get Make Type List
- Get Weight Class Types
- Get Airframe JNIQ Sizes
- Get Aircraft Make List
- Get Aircraft Model List
- Get Company Business Types
- Get Aircraft Company Relationship Types
- Get Event Categories
- Get Event Types
- Get Airport List
- Get State List
- Get Country List
- Get Aircraft Lifecycle Status
- Get Aircraft History Transaction Types
Overview
This node integrates with the JetNet aviation data service to retrieve detailed information about aircraft, companies, contacts, and market intelligence. Specifically, for the Aircraft resource and the Get Flights operation, it fetches the flight history of a specified aircraft by its ID.
Use cases include:
- Tracking historical flight data for an aircraft in fleet management.
- Analyzing usage patterns or operational history for maintenance planning.
- Integrating comprehensive flight records into aviation analytics workflows.
Example: Given an aircraft ID, the node returns all recorded flights associated with that aircraft from the JetNet database.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool's description: - Set Automatically: Description is auto-generated based on resource and operation. - Set Manually: Provide a custom description text. |
| Description | (Shown only if "Set Manually" is selected) A string describing what this tool does, helping language models understand its purpose better. Default: "Access JetNet aviation industry data including aircraft specifications, company information, contact details, and market intelligence". |
Output
The node outputs a JSON string containing:
success: Boolean indicating if the API call was successful.resource: The resource used ("aircraft").operation: The operation performed ("getFlights").data: The flight history data returned from JetNet for the specified aircraft.timestamp: ISO timestamp of when the response was generated.
If the operation fails, the output JSON includes:
success: falseerror: Error message describing the failure.resource,operation, andtimestampas above.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for JetNet with a security token and bearer token for authentication.
- The node makes HTTP requests to the JetNet API endpoint at
https://customer.jetnetconnect.com. - Proper configuration of the API credentials in n8n is necessary for successful calls.
Troubleshooting
Missing Aircraft ID: The operation requires an aircraft ID (
aircraftIdorid). If not provided, the node throws an error: "Aircraft ID is required for this operation".- Resolution: Ensure the input includes a valid aircraft identifier.
Invalid Registration Number: For operations requiring registration number, if the format is incorrect or missing, an error will be thrown.
- Resolution: Provide a valid registration number string.
Authentication Errors: If API credentials are invalid or expired, requests will fail.
- Resolution: Verify and update the API key credentials in n8n.
Unknown Operation or Resource: If unsupported resource or operation values are passed, errors like "Unknown aircraft operation" or "Unknown resource" occur.
- Resolution: Confirm the resource is "aircraft" and operation is "getFlights" for this use case.
API Request Failures: Network issues or JetNet service downtime can cause request failures.
- Resolution: Check network connectivity and JetNet service status.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly included; refer to your JetNet account resources)
- n8n Documentation: Creating Custom Nodes