Actions21
Overview
This node integrates with the PandaDoc API to update an existing contact's information. It allows users to modify various fields of a contact such as email, name, company details, phone number, address, and custom metadata. This is useful in scenarios where contact information needs to be kept current within PandaDoc, for example, updating client details after receiving new information or correcting errors.
Practical examples:
- Automatically update a contact’s email and phone number when they change in your CRM.
- Add or modify metadata associated with a contact for better segmentation or tracking.
- Correct spelling mistakes or update job titles for contacts stored in PandaDoc.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with PandaDoc API: "API Key" or "OAuth2". |
| Contact ID | The unique identifier of the contact to update (required). |
| Update Fields | Collection of fields to update on the contact: |
| Email address of the contact. | |
| - First Name | Contact’s first name. |
| - Last Name | Contact’s last name. |
| - Company | Company name associated with the contact. |
| - Job Title | Contact’s job title. |
| - Phone | Contact’s phone number. |
| - Country | Country of the contact. |
| - State | State or province of the contact. |
| - Postal Code | Postal code of the contact’s address. |
| - Address Line 1 | First line of the contact’s address. |
| - Address Line 2 | Second line of the contact’s address. |
| - Metadata | Custom key-value pairs to add or update metadata associated with the contact. Multiple entries allowed. |
Output
The node outputs an array of JSON objects representing the updated contact(s). Each output item contains the updated contact data as returned by the PandaDoc API. The structure typically includes all contact fields, reflecting the changes made.
If multiple contacts are processed, each will have its own JSON object in the output array.
No binary data output is involved in this operation.
Dependencies
- Requires access to the PandaDoc API.
- Requires authentication via either an API key credential or OAuth2 token configured in n8n.
- The node uses internal helper functions to make authenticated HTTP requests to PandaDoc endpoints.
Troubleshooting
Common issues:
- Invalid or missing Contact ID will cause the update to fail.
- Providing no fields to update may result in no changes or an error.
- Authentication failures due to incorrect API keys or expired OAuth tokens.
- Network or API rate limiting errors from PandaDoc.
Error messages:
"PandaDoc API error: <message>"indicates an issue communicating with the PandaDoc API; check credentials and network connectivity."The operation "update" is not supported for resource "contact"!"would indicate a misconfiguration but should not occur if using this node correctly.- Validation errors from the API if field values do not meet expected formats (e.g., invalid email).
Resolutions:
- Verify that the Contact ID exists and is correct.
- Ensure at least one field is provided in the update collection.
- Confirm that authentication credentials are valid and have necessary permissions.
- Check API limits and retry after some time if rate limited.
Links and References
- PandaDoc API Documentation
- PandaDoc Contacts API Reference (for detailed field info)
- n8n documentation on creating and using API credentials