Actions2
Overview
This node integrates with the Personalia service to create personalized content from document templates or to retrieve template information. It is useful for automating document generation workflows where templates are filled dynamically with user-provided or fetched data. For example, it can generate personalized PDFs, PNGs, or JPGs for contracts, certificates, or marketing materials based on template fields.
Use Case Examples
- Generate a personalized PDF contract by specifying a template ID and providing field values dynamically loaded from the template.
- Retrieve metadata about a specific template to understand which fields are available for personalization.
- Create a personalized image (PNG or JPG) for marketing campaigns with specified output quality settings.
Properties
| Name | Meaning |
|---|---|
| Template ID | ID of the template to use for content creation or information retrieval. |
| Load Template Fields | Whether to load template fields dynamically for easier field value entry during content creation. |
| Output Format | Format of the output file generated (PDF, PNG, or JPG). |
| Quality | Quality setting for the output file, affecting resolution and suitability for print or screen display. |
| Strict Policy | Whether to enforce strict validation of field values against the template's field definitions. |
| Manual Field Entry | Manually enter field names and values for personalization when not loading template fields dynamically. |
| Template Fields | Dynamically loaded template fields for selecting and assigning values during content creation. |
Output
Binary
The node can output the generated personalized content as binary data encoded in base64, including the file name and MIME type, suitable for saving or further processing.
JSON
requestId- The unique request ID for the content creation request.status- The current status of the content creation process (e.g., Completed, Failed).urls- Array of URLs where the generated content can be accessed or downloaded.url- The primary URL of the generated content (first in the URLs array).error- Error message if the content creation failed.detailsstatusCode- Status code associated with an error.errorCode- Specific error code returned by the Personalia API.errorId- Error identifier for tracking.suggestedFix- Suggested fix or guidance for resolving the error.
Dependencies
- Personalia API key credential for authentication with the Personalia service.
Troubleshooting
- Errors related to invalid field values during formatting, such as invalid number, date, or boolean values. The node throws detailed errors indicating which field caused the issue.
- Failures in fetching template information or creating content due to incorrect template ID or invalid API credentials. Users should verify their template ID and API key.
- Timeouts or failures in polling for content generation completion. The node waits and retries but may fail if the service is unresponsive.
- Errors from the Personalia API include error codes and suggested fixes when available, which help diagnose issues.