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
The node provides access to JetNet aviation industry data through a variety of operations on different resources such as Aircraft, Company, Contact, and Market. Specifically, for the Aircraft resource with the Get Condensed Snapshot operation, it retrieves a condensed market snapshot of aircraft data from JetNet.
This node is beneficial in scenarios where users need quick, summarized insights into the aircraft market without retrieving full detailed records. For example, aviation analysts or brokers might use this to get an overview of market conditions or trends for specific aircraft types or segments.
Practical examples:
- Getting a summarized market snapshot for a particular aircraft model or type.
- Quickly accessing key market metrics related to aircraft without fetching exhaustive details.
- Integrating aircraft market intelligence into AI agents or workflows for decision support.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool description: - Set Automatically: The description is set based on the selected resource and operation. - Set Manually: Allows manual input of a custom description explaining what the tool does. |
| Description | (Shown only if "Set Manually" is chosen) A string describing the tool's purpose, e.g., "Access JetNet aviation industry data including aircraft specifications, company information, contact details, and market intelligence". |
Output
The node outputs a JSON object with the following structure:
{
"success": true,
"resource": "aircraft",
"operation": "getCondensedSnapshot",
"data": { /* Condensed aircraft market snapshot data returned by JetNet API */ },
"timestamp": "ISO 8601 timestamp"
}
success: Boolean indicating if the API call was successful.resource: The resource queried ("aircraft").operation: The operation performed ("getCondensedSnapshot").data: Contains the condensed snapshot data retrieved from JetNet. This includes summarized market information about aircraft.timestamp: The time when the response was generated.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the JetNet service.
- The node makes HTTP requests to the JetNet API endpoint at
https://customer.jetnetconnect.com. - Proper configuration of the API authentication token and bearer token is necessary within n8n credentials.
- Network connectivity to JetNet API endpoints is required.
Troubleshooting
- Missing Required Parameters: If required parameters like aircraft ID or registration number are missing for other operations, the node throws errors indicating which parameter is needed. For "Get Condensed Snapshot", no specific ID is required, but ensure correct resource and operation selection.
- Unknown Resource or Operation: Errors will be thrown if an unsupported resource or operation is specified.
- Authentication Errors: If API credentials are invalid or expired, requests will fail. Verify that the API key and tokens are correctly configured.
- Network Issues: Connectivity problems to the JetNet API endpoint can cause request failures.
- Malformed Input: Input data should be valid JSON or strings parsable to JSON; otherwise, errors may occur.
To resolve errors:
- Double-check input parameters and their presence.
- Confirm API credentials and permissions.
- Ensure network access to JetNet services.
- Review error messages returned in the JSON output for guidance.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly provided here; consult your JetNet account or support)
- n8n Documentation on creating and using API key credentials and HTTP Request nodes for reference on authentication setup