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 JetNet aviation market intelligence data, specifically for the "Market" resource and the "Get Aircraft History Transaction Types" operation. It retrieves a list of aircraft history transaction types from the JetNet database. This information is useful for users who need detailed historical transaction categorizations related to aircraft, such as sales, leases, or other ownership changes.
Common scenarios where this node is beneficial include:
- Aviation market analysts tracking transaction trends.
- Aircraft brokers or dealers needing standardized transaction type references.
- Developers building aviation data applications requiring detailed transaction metadata.
Example use case: Fetching all possible aircraft history transaction types to populate dropdowns in an aviation management system or to validate transaction records against known categories.
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: You provide a custom description explaining what the tool does. |
| Description | (Shown only if "Set Manually" is chosen) A text field to manually describe the tool's purpose to improve AI agent understanding. 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 name ("market").operation: The operation name ("getAircraftHistoryTransTypes").data: The actual list of aircraft history transaction types retrieved from JetNet.timestamp: ISO timestamp of when the response was generated.
The output JSON structure looks like this (formatted for clarity):
{
"success": true,
"resource": "market",
"operation": "getAircraftHistoryTransTypes",
"data": [ /* array of aircraft history transaction types */ ],
"timestamp": "2024-06-xxTxx:xx:xx.xxxZ"
}
No binary data output is involved in 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 access to JetNet API endpoints must be available.
Troubleshooting
- Missing or invalid credentials: If the API key or tokens are not configured correctly, the node will fail to authenticate. Ensure that valid JetNet API credentials are set up in n8n.
- Unknown resource or operation error: Selecting a resource or operation not supported by the node will throw an error. Confirm that "market" is selected as the resource and "Get Aircraft History Transaction Types" as the operation.
- API request failures: Network issues or JetNet service downtime can cause errors. Check network connectivity and JetNet service status.
- Malformed input parameters: Although this operation requires no additional input parameters, providing unexpected inputs may cause errors.
Error messages returned by the node include descriptive messages such as:
"Unknown market operation: ..."if an unsupported operation is requested."Unknown resource: ..."if an unsupported resource is specified.- API error messages propagated from JetNet, which should be reviewed for troubleshooting.
Links and References
- JetNet official website: https://www.jetnet.com/
- JetNet API documentation (if publicly available, check with JetNet support)
- n8n documentation on creating and using API credentials: https://docs.n8n.io/credentials/overview/