JetNet icon

JetNet

Interact with JetNet API for aviation industry data
Join our community

Actions44

Overview

This node interacts with the JetNet API to retrieve paginated lists of contact information within the aviation industry. It is designed to fetch contacts based on various filtering criteria and supports pagination to handle large datasets efficiently.

Typical use cases include:

  • Retrieving a specific page of contacts filtered by aircraft IDs, company details, names, titles, or other attributes.
  • Integrating contact data into workflows for marketing, outreach, or CRM synchronization.
  • Managing large contact lists by fetching them in manageable pages rather than all at once.

For example, a user might want to get the second page of contacts who are associated with a particular company and have a certain job title, limiting results to 100 per page.

Properties

Name Meaning
Page Size Number of results per page (0 means retrieve all results). Range: 0 to 1000.
Page Page number to retrieve (0 means retrieve all results). Minimum value is 0.
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.
- Phone Number Filter contacts by phone number.
- Contact Changes Boolean flag indicating whether to include contact changes in the results.
- 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 representing contacts matching the specified filters and pagination parameters. Each item corresponds to a single contact record as returned by the JetNet API.

The structure of each contact object depends on the API response but typically includes fields such as contact identifiers, names, company affiliations, contact details, and related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the JetNet API via an API key credential configured in n8n.
  • The node sends HTTP requests to https://customer.jetnetconnect.com endpoints.
  • Proper API authentication token must be provided through the node's credentials configuration.

Troubleshooting

  • Empty Results: If no contacts are returned, verify that the filter criteria in "Additional Fields" are correct and not overly restrictive.
  • Invalid Page or Page Size: Ensure that "Page" and "Page Size" values are within allowed ranges (Page ≥ 0, Page Size between 0 and 1000).
  • Authentication Errors: Confirm that the API key credential is valid and has necessary permissions.
  • API Rate Limits: Large page sizes or frequent requests may hit API rate limits; consider reducing page size or adding delays.
  • Error Messages: The node surfaces error messages from the API. Common errors include invalid parameters or unauthorized access. Review the error message and adjust parameters or credentials accordingly.

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 underlying request mechanics

Discussion