Actions28
- Companies Actions
- Products Actions
- Orders Actions
- Subscriptions Actions
- Contacts Actions
- Invoices Actions
- Usage Summaries Actions
Overview
This node is designed to fetch detailed information about a specific contact within a company using their unique identifiers. It is particularly useful in scenarios where you need to retrieve up-to-date contact details from a partner or customer database, such as for CRM updates, support ticket enrichment, or automated workflows that require contact validation.
For example, if you have a company ID and a contact ID, this node will query the external service's API to return the full contact record associated with those IDs.
Properties
| Name | Meaning |
|---|---|
| Company Id | The unique identifier of the company to which the contact belongs. |
| Contact Id | The unique identifier of the contact whose details you want to fetch. |
Output
The node outputs a JSON object containing the full details of the requested contact. This typically includes fields such as name, email, phone number, role, and other metadata related to the contact within the specified company.
If the node supports binary data output (not evident from the provided code), it would represent any file attachments or media related to the contact, but based on the static analysis, the output is primarily JSON data representing contact information.
Dependencies
- Requires an API key credential for authenticating requests to the external Pax8 Partner API.
- The base URL for API requests is
https://api.pax8.com/v1. - The node depends on the
@avantguardllc/n8n-openapi-nodepackage and a local OpenAPI specification file (openapi-pax8-partner.json) to build its properties and handle API interactions.
Troubleshooting
Common Issues:
- Invalid or missing Company Id or Contact Id will result in errors or empty responses.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity issues preventing access to the external API endpoint.
Error Messages:
- Unauthorized or 401 errors indicate problems with the API key; verify and update credentials.
- 404 Not Found errors suggest that either the company or contact ID does not exist or is incorrect.
- Timeout or network errors may require checking your internet connection or proxy settings.
Links and References
- Pax8 API Documentation (general reference for the external API)
- n8n Documentation for guidance on setting up credentials and using custom nodes