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 integrates with the JetNet API to retrieve detailed aviation industry data related to contacts. Specifically, the "Contact" resource with the "Get" operation fetches all available information about a contact by their unique ID. This is useful for workflows that need to enrich data with contact details such as names, roles, or other metadata associated with aviation contacts.
Practical scenarios include:
- Retrieving contact details for an individual in an aviation company.
- Enriching CRM records with up-to-date contact information from JetNet.
- Automating communications or reporting based on contact data.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve information for. |
Output
The node outputs JSON data representing the full details of the specified contact as returned by the JetNet API. The structure typically includes fields such as name, contact information, relationships, and other metadata relevant to the contact within the aviation industry.
If multiple contacts were retrieved (not applicable for this single-get operation), each would be output as a separate JSON object. No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the JetNet API via an API key credential configured in n8n.
- The node makes HTTP GET requests to the JetNet API endpoints.
- Network access to
https://customer.jetnetconnect.commust be available.
Troubleshooting
Common issues:
- Invalid or missing Contact ID will cause the API request to fail.
- Expired or incorrect API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors from the API are caught and reported as node execution errors.
- If "Continue On Fail" is enabled, errors will be included in the output JSON under an
errorfield for the respective item.
Resolutions:
- Verify the Contact ID is correct and exists in JetNet.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and firewall settings.
Links and References
- JetNet Official Website — For more information about the JetNet service.
- JetNet API documentation (not publicly linked here) — Consult your JetNet account representative for API docs and endpoint details.