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 provides access to detailed aviation data from the JetNet database, specifically for the Aircraft resource and its various operations. The "Get Additional Equipment" operation retrieves detailed information about additional equipment installed on a specific aircraft identified by its ID.
Typical use cases include:
- Aviation industry analysts or companies needing comprehensive aircraft equipment details.
- Maintenance teams verifying installed additional equipment on aircraft.
- Market intelligence services requiring enriched aircraft profiles.
For example, a user can input an aircraft ID to fetch all additional equipment details associated with that aircraft, enabling informed decision-making or reporting.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool description: - Set Automatically: Description is auto-generated based on resource and operation. - Set Manually: User provides a custom description explaining what the tool does. |
| Description | (Shown only if "Set Manually" is selected) A text field where you specify a detailed description of the tool's purpose, helping language models understand the tool better. Default is: "Access JetNet aviation industry data including aircraft specifications, company information, contact details, and market intelligence". |
Output
The node outputs a JSON string containing the following structure:
{
"success": true,
"resource": "aircraft",
"operation": "getAdditionalEquipment",
"data": { /* Detailed additional equipment data returned from JetNet API */ },
"timestamp": "ISO 8601 timestamp"
}
success: Boolean indicating whether the API call was successful.resource: The resource queried ("aircraft").operation: The operation performed ("getAdditionalEquipment").data: The actual additional equipment details retrieved from the JetNet API for the specified aircraft.timestamp: The time when the response was generated.
If an error occurs, the output JSON will have "success": false and an "error" message describing the issue.
The node does not output binary data.
Dependencies
- Requires an active connection to the JetNet API service.
- Requires an API authentication token and security token configured in n8n credentials (referred generically as "an API key credential").
- The node makes HTTP requests to the JetNet API endpoints under
https://customer.jetnetconnect.com.
Troubleshooting
- Missing Aircraft ID: The operation requires an aircraft ID. If this is not provided, the node throws an error: "Aircraft ID is required for this operation".
- Invalid Operation or Resource: If an unsupported operation or resource is specified, the node throws errors like "Unknown aircraft operation" or "Unknown resource".
- Authentication Errors: If API credentials are missing or invalid, HTTP requests will fail. Ensure the API key and tokens are correctly configured.
- Network Issues: Connectivity problems to the JetNet API endpoint may cause request failures.
- Malformed Input: If input parameters are incorrectly formatted or missing required fields, the node may return error messages indicating the problem.
To resolve these issues:
- Verify all required input parameters are provided and valid.
- Confirm API credentials are properly set up in n8n.
- Check network connectivity to the JetNet API.
- Review error messages returned in the output JSON for specific guidance.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account resources)
- n8n HTTP Request node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/