JetNet icon

JetNet

Interact with JetNet API for aviation industry data
Join our community

Actions44

Overview

The node interacts with the JetNet API to retrieve aviation industry data related to contacts. Specifically, for the "Contact" resource and "Get List" operation, it fetches a list of contact records filtered by various criteria such as aircraft IDs, company details, names, titles, emails, phone numbers, and more. This operation is useful when you want to obtain multiple contact entries matching specific filters, for example, retrieving all contacts associated with certain companies or aircraft.

Practical examples:

  • Fetching all contacts linked to a particular company or set of companies.
  • Retrieving contacts who have a specific job title or email domain.
  • Getting contacts related to certain aircraft IDs for targeted communications or analysis.

Properties

Name Meaning
Return All Whether to return all matching results or limit the number of returned contacts.
Limit Maximum number of contacts to return if not returning all (range 1-1000).
Additional Fields Collection of optional filters to narrow down the contact list:
- Aircraft IDs Filter contacts by one or more aircraft IDs.
- Company ID Filter contacts by a specific company ID.
- Company Name Filter contacts by company name.
- First Name Filter contacts by first name.
- Last Name Filter contacts by last name.
- Title Filter contacts by contact title/job position.
- Email Filter contacts by email address.
- Action Date Filter contacts by action date (likely last update or activity date).
- Phone Number Filter contacts by phone number.
- Contact Changes Boolean flag to include only contacts with changes.
- Contact List Filter by a list of specific contact IDs.
- Company List Filter by a list of specific company IDs.

Output

The output is an array of JSON objects, each representing a contact record retrieved from the JetNet API. Each object contains detailed contact information according to the applied filters. The exact structure depends on the API response but typically includes fields like contact identifiers, names, company associations, contact details (email, phone), titles, and possibly metadata about recent changes.

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 sends HTTP POST requests to the endpoint /api/Contact/getContactList/{API_TOKEN} with filter parameters in the request body.
  • Proper API authentication token must be provided through the node's credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause authorization errors.
    • Providing invalid filter values (e.g., non-existent company or aircraft IDs) may result in empty responses.
    • Exceeding API rate limits could lead to temporary blocking or errors.
    • Setting Return All to false but specifying a very high Limit might cause performance delays.

  • Error messages:

    • Authorization errors: Check that the API key credential is correctly configured and valid.
    • Network or timeout errors: Verify network connectivity and API availability.
    • Validation errors: Ensure filter parameters conform to expected types and formats.

Links and References

Discussion