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 export aircraft data in paged bulk format. Specifically, the "Get Bulk Aircraft Export Paged" operation allows users to retrieve large sets of aircraft data divided into manageable pages, which is useful for processing or analyzing extensive datasets without overwhelming system resources.
Common scenarios where this node is beneficial include:
- Aviation market analysts needing comprehensive aircraft data segmented by pages.
- Developers building applications that require incremental loading of aircraft information.
- Data engineers exporting aircraft records for ETL (Extract, Transform, Load) pipelines.
Practical example: A user wants to download all aircraft data but prefers to fetch it in batches of 100 records per page to avoid timeouts or memory issues. They configure the node to use the "Get Bulk Aircraft Export Paged" operation and specify the page size and page number parameters accordingly.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool's description: either automatically based on resource and operation, or manually by entering a custom description. |
| Description | When manual description is selected, provide a specific explanation of what this tool does to help AI agents produce better results. |
Output
The node outputs JSON data structured as follows:
{
"success": true,
"resource": "aircraft",
"operation": "getBulkAircraftExportPaged",
"data": { /* The paged aircraft data returned from JetNet API */ },
"timestamp": "ISO 8601 timestamp string"
}
success: Indicates whether the API call was successful.resource: The resource type, here always "aircraft".operation: The operation performed, here "getBulkAircraftExportPaged".data: Contains the actual aircraft data for the requested page, as returned by the JetNet API.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 aviation data service.
- The node makes HTTP requests to the JetNet API endpoint at
https://customer.jetnetconnect.com. - Proper configuration of the API authentication token and security token is necessary within n8n credentials.
Troubleshooting
- Missing or invalid credentials: If the API key or tokens are not configured correctly, the node will fail to authenticate. Ensure valid credentials are set up in n8n.
- Required parameters missing: For this operation, pagination parameters such as
pageSizeandpageshould be provided; otherwise, defaults (pageSize=100, page=1) are used. Supplying invalid values may cause errors. - Unknown resource or operation error: This node only supports predefined resources and operations. Using unsupported combinations will throw errors.
- API request failures: Network issues or JetNet service downtime can cause request failures. Check connectivity and JetNet service status.
- Error messages: The node returns error details in the output JSON under the
errorfield. Common messages include missing IDs or registration numbers for other operations, but for this operation, ensure pagination parameters are correct.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account or support)
- n8n Documentation on creating and using custom nodes: https://docs.n8n.io/creating-nodes/