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 to create new entities within the system. This node is useful in scenarios where you need to automate the creation of records (entities) in QContact from other workflows or data sources. For example, you might use this node to automatically add new contacts, companies, or custom entity types when receiving data from web forms, CRMs, or other business tools.

Properties

Name Type Meaning
Entity options Selects the type of entity to create (e.g., Contact, Company). Options are dynamically loaded.
As JSON boolean If enabled, allows providing all parameters as a single JSON object instead of individual fields.
JSON json The JSON object containing all parameters for the entity. Only shown if "As JSON" is enabled.
Fields fixedCollection Allows specifying individual fields and their values for the entity. Only shown if "As JSON" is disabled.

Output

  • The node outputs a json field containing the result of the entity creation operation.
  • The structure of the output will typically include details about the newly created entity, such as its ID and any returned properties from the QContact API.
  • No binary data is produced by this node.

Dependencies

  • External Service: Requires access to the QContact API.
  • API Key/Credentials: You must configure valid QContact API credentials in n8n under the name qContactApi.
  • n8n Configuration: Ensure that the QContact node is properly installed and that credentials are set up and tested.

Troubleshooting

  • Invalid Credentials: If your API key or credentials are incorrect, the node may throw authentication errors. Double-check your credential setup in n8n.
  • Missing Required Fields: If required fields for the selected entity type are not provided, the API may return validation errors. Review the entity's documentation for required fields.
  • Malformed JSON: When using the "As JSON" option, ensure your JSON input is correctly formatted. Malformed JSON will cause parsing errors.
  • Unknown Entity Type: If the "Entity" dropdown does not show expected options, there may be an issue loading entity types from the API.

Links and References

Discussion