PandaDoc icon

PandaDoc

Consume PandaDoc API

Actions21

Overview

This node integrates with the PandaDoc API to manage contacts, documents, folders, and templates. Specifically, for the Contact - Get operation, it retrieves detailed information about a single contact by its unique ID. This is useful in scenarios where you need to fetch up-to-date contact details from PandaDoc within an automated workflow, such as syncing contact data, triggering document generation based on contact info, or auditing contact records.

Practical example:
You have a CRM system integrated with n8n and want to enrich your contact records with additional data stored in PandaDoc. Using this node’s Contact Get operation, you can retrieve a contact’s full profile by their ID and use that data downstream in your workflow.

Properties

Name Meaning
Authentication Method of authenticating with PandaDoc API. Options: API Key, OAuth2.
Contact ID The unique identifier of the contact to retrieve. This is required for the Get operation.

Output

The node outputs JSON data representing the contact object retrieved from PandaDoc. The structure typically includes all available fields of the contact such as name, email, phone number, company, and any custom fields defined in PandaDoc.

  • The output is an array of items, each with a json property containing the contact data.
  • No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "json": {
    "id": "contact_id_value",
    "first_name": "John",
    "last_name": "Doe",
    "email": "[email protected]",
    "phone": "+1234567890",
    "company": "Example Inc.",
    ...
  }
}

Dependencies

  • Requires a valid PandaDoc API authentication credential, either via an API key or OAuth2 token.
  • The node depends on the PandaDoc REST API being accessible.
  • No additional environment variables are needed beyond the configured credentials.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication errors.
    • Providing a non-existent or incorrect Contact ID will result in an error indicating the contact was not found.
    • Network connectivity problems may cause request timeouts or failures.

  • Error messages:

    • "PandaDoc API error: <message>" indicates an issue returned by the PandaDoc API, such as invalid parameters or authentication failure.
    • "The operation "get" is not supported for resource "contact"!" would occur if the operation is incorrectly specified.

  • Resolutions:

    • Verify that the API key or OAuth2 token is correct and has sufficient permissions.
    • Double-check the Contact ID value for correctness.
    • Ensure network access to the PandaDoc API endpoint.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

Discussion