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 industry data, specifically for the Contact resource with the Get operation. It allows users to retrieve detailed contact information by a unique contact ID from the JetNet database. This is useful in scenarios where you need to fetch comprehensive contact details related to aviation companies or personnel, such as for sales outreach, customer support, or market research.
Practical examples include:
- Retrieving contact details of an aviation company representative.
- Accessing contact information for maintenance or operational staff linked to aircraft.
- Integrating contact data into CRM systems or AI agents that assist with aviation-related queries.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to set the tool description: - Set Automatically: The description is set based on the resource and operation. - Set Manually: You provide a custom description explaining what this tool does. |
| Description | (Shown only if "Set Manually" is selected) A text field to describe the tool's purpose to improve LLM results. Default: "Access JetNet aviation industry data including aircraft specifications, company information, contact details, and market intelligence". |
Output
The node outputs a JSON string containing the following structure:
{
"success": true,
"resource": "contact",
"operation": "get",
"data": { /* Contact data object returned from JetNet API */ },
"timestamp": "ISO 8601 timestamp"
}
success: Boolean indicating if the API call was successful.resource: The resource type, here always"contact".operation: The operation performed, here"get".data: The detailed contact information retrieved from JetNet, structured as per JetNet's API response.timestamp: The time when the response was generated.
If an error occurs, the output JSON will have success set to false and include an error message describing the issue.
The node does not output binary data.
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.
Troubleshooting
- Missing Contact ID: The operation requires a valid contact ID (
contactIdorid). If missing, the node throws an error:"Contact ID is required for this operation". Ensure you provide this parameter. - Invalid Credentials: Authentication failures may occur if the API key or tokens are incorrect or expired. Verify your API credentials in n8n.
- Unknown Operation or Resource: Errors like
"Unknown contact operation"or"Unknown resource"indicate misconfiguration of the resource or operation parameters. - API Request Failures: Network issues or JetNet API downtime can cause request failures. Check connectivity and JetNet service status.
- Malformed Input: If input data is not properly formatted JSON or lacks required fields, the node may fail to parse or execute correctly.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly provided here; refer to your JetNet account resources)
- n8n Documentation: Creating Custom Nodes