Actions4
- Allocation Actions
- Certificate Actions
Overview
This node integrates with the Dots.eco API to create a certificate representing a user's environmental or social impact. It is useful in scenarios where organizations want to issue verifiable certificates for contributions, donations, or other impactful actions tracked by Dots.eco. For example, a company could automate issuing certificates to users who have contributed to carbon offset projects or other sustainability initiatives.
The "Create Certificate" operation sends user and impact details to the Dots.eco platform, which then generates a certificate that can optionally be emailed to the user.
Properties
| Name | Meaning |
|---|---|
| Application Token | Mandatory string: The application ID and first part of the application UUID from Dots.eco, found in the app dashboard. |
| Impact Quantity | Mandatory integer (as string): The quantity representing the user's impact (e.g., amount of CO2 offset). |
| Allocation ID | Mandatory integer (as string): The allocation ID related to the impact source or project. |
| Name on the Certificate | Optional string: The name of the user for whom the certificate is issued. |
| Remote User ID | Mandatory string: Identifier provided by the client to identify the user receiving the certificate. If no existing user matches this ID, a new user will be created. |
| Remote User Email | Optional string (valid email): Email assigned if a new user is created. If not provided, an email in the format {remote_user_id}@dots.eco will be generated automatically. |
| Certificate Design | Optional string: Custom value passed to the certificate template; requires coordination with the Dots.eco team to take effect. |
| Send Certificate by Email | Optional string: If set to "yes", the certificate notification will be sent to the remote user's email address. |
| Certificate Info | Optional string: Additional information such as transaction or order ID associated with the certificate issuance. |
| Langcode | Optional string: Language code to return the response in the specified language. |
| Currency | Optional string: Currency code to set the currency context for the certificate. |
Output
The node outputs a JSON array containing the response from the Dots.eco API after attempting to create the certificate. This response typically includes details about the newly created certificate, such as its unique identifier, status, and any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Dots.eco API.
- Requires configuration of credentials including:
- Base URL of the Dots.eco API.
- An API authentication token or key (configured in n8n credentials).
- The node uses authenticated HTTP requests to communicate with the Dots.eco service.
Troubleshooting
- Missing or invalid API base URL: The node throws an error if the API base URL is not configured in the credentials. Ensure the base URL is correctly set.
- Authentication errors: If the API key or token is invalid or missing, requests will fail. Verify credentials are correct and have necessary permissions.
- Invalid or missing mandatory parameters: The operation requires certain fields like
app_token,impact_qty,allocation_id, andremote_user_id. Omitting these will likely cause API errors. - Email sending issues: If
send_certificate_by_emailis set to "yes" but the remote user email is invalid or missing, the email notification may fail or be sent to a default generated email. - API response errors: Any errors returned by the Dots.eco API (e.g., invalid allocation ID) will be included in the node's output. Review the API documentation or contact Dots.eco support for specific error codes.
Links and References
- Dots.eco Official Website
- Dots.eco API Documentation (Assumed, please verify actual link)
- n8n Documentation on Creating Custom Nodes