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 Event List operation, it fetches a list of events related to a particular aircraft from the JetNet database.
Use cases include:
- Accessing historical or recent event data for an aircraft, such as maintenance events, incidents, or other logged activities.
- Integrating aviation event data into workflows for monitoring aircraft status or history.
- Enriching aviation-related datasets with event details for analysis or reporting.
Example: You want to get all recorded events for a specific aircraft identified by its ID to analyze its maintenance and operational history.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool description: either automatically based on resource and operation, or manually provide a custom description. |
| Description | (Shown only if "Set Manually" is selected) A text description explaining what this tool does, useful for guiding AI agents. Default explains access to JetNet aviation data including aircraft specifications, company info, contacts, and market intelligence. |
Output
The node outputs a JSON string containing:
success: Boolean indicating if the API call was successful.resource: The resource type used ("aircraft").operation: The operation performed ("getEventList").data: The actual event list data returned from JetNet API for the aircraft.timestamp: ISO timestamp of when the response was generated.
If the API call fails, the output JSON includes:
success: falseerror: Error message describing the failure.resource,operation, andtimestampfields as above.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for JetNet's API authentication.
- The node makes HTTP requests to JetNet's customer API endpoint (
https://customer.jetnetconnect.com). - Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
- Missing Aircraft ID: The "Get Event List" operation requires identifying the aircraft, typically via an aircraft ID or parameters passed in the input. If missing, the node will throw an error indicating the required ID is not provided.
- Authentication Errors: If the API key or token is invalid or expired, the node will fail to authenticate with JetNet, resulting in errors. Ensure the API credentials are correctly configured and valid.
- Unknown Operation or Resource: If the resource or operation name is incorrect or unsupported, the node throws an error specifying the unknown resource or operation.
- Network Issues: Connectivity problems to the JetNet API endpoint can cause request failures. Verify network access and endpoint availability.
- Malformed Input: Input parameters must be properly structured; otherwise, the node may fail to parse them or construct the API request correctly.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account or support for API docs)
- n8n Documentation: Creating Custom Nodes