Overview
This node, named "Certificate Generator," is designed to send certificate details via a POST HTTP request to a specified local API endpoint (http://localhost:3000/api). It collects certificate information such as the recipient's name, the signer, and the validity period (start and end dates), then sends this data to an external service for processing or storage.
Common scenarios where this node would be beneficial include:
- Automating the generation and registration of certificates in an internal system.
- Integrating with a custom certificate management API to track issued certificates.
- Sending certificate data to a microservice that handles certificate creation or validation.
For example, a user could input the name of a course participant, the authority who signed the certificate, and the validity dates. The node will then forward this information to the backend service, which might generate a PDF certificate or store the record.
Properties
| Name | Meaning |
|---|---|
| Name | The full name of the certificate recipient. |
| Signed By | The name of the person or entity who signed or authorized the certificate. |
| Start Date | The starting date from which the certificate is valid. |
| End Date | The ending date until which the certificate remains valid. |
Output
The node outputs an array of JSON objects, each representing the response received from the HTTP POST request to the external API. Each output item contains the full JSON response returned by the API after sending the certificate details.
No binary data output is produced by this node.
Dependencies
- Requires access to an HTTP endpoint at
http://localhost:3000/apithat accepts POST requests with certificate details in JSON format. - No special authentication or API keys are handled within the node; if the API requires authentication, it must be managed externally or added to the HTTP request configuration.
- The node uses built-in HTTP request helper methods provided by the n8n framework.
Troubleshooting
- Connection errors: If the node cannot reach
http://localhost:3000/api, ensure the target server is running and accessible from the n8n instance. - Invalid responses: If the API returns errors, verify that all required properties (
Name,Signed By,Start Date,End Date) are correctly set and formatted. - Date formatting issues: Ensure that the start and end dates are valid ISO 8601 date-time strings, as improper formats may cause the API to reject the request.
- Unhandled exceptions: The node throws a generic operation error if the HTTP request fails; checking the error message can help identify network or API issues.