Actions44
- Contact Actions
- 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 Paged
- Get Condensed Owner Operators Paged
- Get Event List Paged
- Get History List Paged
- Company Actions
- Market Actions
Overview
This node interacts with the JetNet API to retrieve aviation industry data related to aircraft. Specifically, the "Get Bulk Aircraft Export Paged" operation allows users to export large sets of aircraft data in paginated form. This is useful when dealing with extensive aircraft datasets that cannot be retrieved in a single request due to size or performance constraints.
Typical use cases include:
- Exporting aircraft data for analysis or reporting in manageable chunks.
- Integrating bulk aircraft information into other systems or databases.
- Incrementally processing large aircraft datasets by page.
For example, a user might set the page size to 100 and request page 1 to get the first 100 aircraft records, then iterate through subsequent pages to process all available data.
Properties
| Name | Meaning |
|---|---|
| Page Size | Number of results per page (minimum 1, maximum 1000). Controls how many aircraft records are returned in one page. |
| Page | Page number to retrieve (minimum 1). Specifies which page of results to fetch. |
Output
The output is a JSON array where each item corresponds to an aircraft record from the bulk export. Each JSON object contains detailed aircraft data as provided by the JetNet API.
- The structure of each JSON object depends on the API response but generally includes comprehensive aircraft details.
- No binary data is output by this operation.
Example output snippet (simplified):
[
{
"aircraftId": 12345,
"make": "GULFSTREAM",
"model": "G550",
"yearManufactured": 2015,
...
},
{
"aircraftId": 12346,
"make": "BOEING",
"model": "737",
"yearManufactured": 2018,
...
}
]
Dependencies
- Requires an API key credential for authenticating with the JetNet API.
- The node uses the base URL
https://customer.jetnetconnect.com. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Requesting a page number beyond the available range may return empty results.
- Setting a page size outside the allowed range (less than 1 or greater than 1000) may cause errors.
Error messages:
- Authentication errors typically indicate invalid or expired API credentials; verify and update your API key.
- Validation errors on parameters suggest incorrect page size or page number values; ensure they meet the specified constraints.
- Network or timeout errors may occur if the API service is unreachable; check network connectivity and JetNet service status.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account resources)
- n8n Documentation on HTTP Request Node for understanding API calls in workflows