QContact icon

QContact

Consume QContact API (v.0.1.3)

Actions7

Overview

The "QContact" node for n8n allows users to interact with the QContact API. Specifically, when using the Entities resource and the Retrieve operation, this node retrieves a specific entity from QContact by its type and unique identifier. This is useful in scenarios where you need to fetch detailed information about a particular entity (such as a contact, company, or other record) stored in QContact, for use in further automation steps.

Practical examples:

  • Fetching a customer's details by their ID to personalize an email.
  • Retrieving a company's profile before updating related records.
  • Pulling entity data to synchronize with another system.

Properties

Name Type Meaning
Entity options The type of entity to retrieve (e.g., Contact, Company). Options are dynamically loaded.
ID number The unique identifier of the entity to retrieve.

Output

The node outputs a json object containing the retrieved entity's data. The exact structure depends on the selected entity type but typically includes all fields associated with that entity in QContact.

If the node supports binary output, it is not indicated in the provided code.

Dependencies

  • External Service: Requires access to the QContact API.
  • Credentials: Needs a configured "qContactApi" credential in n8n.
  • Environment Variables/Config: None specified, but API credentials must be set up in n8n.

Troubleshooting

Common Issues:

  • Invalid Credentials: If the "qContactApi" credentials are missing or incorrect, authentication will fail.
  • Entity Not Found: Providing an invalid or non-existent ID may result in errors or empty results.
  • API Connectivity: Network issues or incorrect API endpoint configuration can cause failures.

Error Messages & Resolutions:

  • "Authentication failed" – Check your QContact API credentials in n8n.
  • "Entity not found" – Verify the ID and entity type are correct and exist in QContact.
  • "Network error" – Ensure n8n has internet access and the QContact API is reachable.

Links and References

Discussion