Overview
This node acts as a trigger for PandaDoc events related to documents. It listens for specific document-related webhook events such as changes in document state, updates, views by recipients, or completion by all recipients. When one of these events occurs, the node activates the workflow, optionally fetching detailed document information.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a document is viewed or completed.
- Tracking document lifecycle changes (e.g., from draft to sent).
- Synchronizing document updates with other systems.
- Sending notifications or logging events based on document activity.
For example, you could use this node to start a workflow that sends a thank-you email once a document is completed by all recipients or update a CRM record when a document is viewed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests: "API Key" or "OAuth2". |
| Event | The specific PandaDoc event to listen for: - Document State Changed - Document Updated - Document Viewed - Document Completed |
| Options | Additional settings: - Include Document Details: Whether to fetch and include full document details. - Only For Workspace: Filter events to a specific workspace ID. |
| Webhook Name | Optional name assigned to the webhook created for this trigger. |
Output
The node outputs JSON data representing the webhook event payload received from PandaDoc. The structure includes at least:
event: The type of event triggered.data: Core event data related to the document.
If the option Include Document Details is enabled and the event data contains a document ID, the node makes an additional API call to fetch comprehensive document details and adds them under the documentDetails field in the output JSON.
The output is always delivered as a JSON array containing a single object with the event data and optional document details.
No binary data output is produced by this node.
Dependencies
- Requires access to PandaDoc API via either an API key or OAuth2 authentication.
- Needs proper configuration of credentials within n8n for authentication.
- The node creates and manages webhooks on PandaDoc, so the PandaDoc account must allow webhook creation.
- Network connectivity to PandaDoc API endpoints is necessary.
Troubleshooting
- Webhook Creation Failure: If the node fails to create a webhook, ensure the provided API credentials have sufficient permissions and that the workspace ID (if specified) is valid.
- Webhook Not Triggering: Verify that the PandaDoc webhook URL configured in the node is reachable and correctly set up in PandaDoc.
- Failed to Fetch Document Details: When enabling the option to include document details, failures may occur if the document ID is missing or the API credentials lack read permissions. Check logs for error messages.
- Invalid Event Data: If the incoming webhook payload lacks expected fields (
eventordata), the node will ignore it. Ensure PandaDoc is sending correct event payloads. - Authentication Errors: Confirm that the selected authentication method matches the configured credentials and that tokens or keys are valid and not expired.