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 aviation-related information. Specifically, for the Company resource and the Get Company History operation, it fetches historical and transaction records related to a company from the JetNet database.
This node is beneficial in scenarios where users need comprehensive historical data about aviation companies, such as transaction histories, ownership changes, or other significant events recorded by JetNet. For example, an aviation market analyst might use this node to gather company history data to assess company stability or track past transactions.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool's description: - Set Automatically: The description is auto-generated based on the selected resource and operation. - Set Manually: Allows manual input of a custom description explaining what the tool does. |
| Description | A text field to manually describe what the tool does. This is only shown if "Set Manually" is selected for Tool Description. It helps Large Language Models (LLMs) understand the tool’s purpose better. Default: "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": "company",
"operation": "getCompanyHistory",
"data": { /* Company history and transaction records from JetNet */ },
"timestamp": "ISO 8601 timestamp"
}
success: Boolean indicating whether the API call was successful.resource: The resource queried, here always"company".operation: The operation performed, here"getCompanyHistory".data: Contains the actual company history and transaction records returned by JetNet.timestamp: The time when the response was generated.
If an error occurs, the output JSON will have:
{
"success": false,
"error": "Error message describing the problem",
"resource": "company",
"operation": "getCompanyHistory",
"timestamp": "ISO 8601 timestamp"
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the JetNet API service.
- Needs an API authentication token and security token configured in n8n credentials for JetNet.
- The node makes HTTP requests to the JetNet customer API endpoint (
https://customer.jetnetconnect.com).
Troubleshooting
- Missing Company ID: The operation requires a valid company ID or identifier in the input parameters. If missing, the node throws an error:
"Company ID is required for this operation". Ensure you provide the correct company ID. - Unknown Operation or Resource: If the resource or operation name is incorrect or unsupported, errors like
"Unknown company operation"or"Unknown resource"may occur. Verify that the resource is set to"company"and operation to"getCompanyHistory". - Authentication Errors: If API credentials are invalid or expired, the node will fail to authenticate. Check your API key and security token configuration.
- API Request Failures: Network issues or JetNet service downtime can cause request failures. Review error messages and retry later if needed.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly included; consult your JetNet account representative)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/