Overview
This node triggers when a donation is confirmed on the Charity's Purse platform. It periodically polls the Charity's Purse API to check for new confirmed donations since the last poll time and emits these as output items. This trigger node is useful in workflows that need to react to confirmed donations, such as sending thank-you emails, updating donor databases, or triggering other automation based on donation events.
Practical examples:
- Automatically send a personalized thank-you email whenever a donation is confirmed.
- Update a CRM system with new donor information upon confirmation of a donation.
- Trigger accounting or reporting workflows when new donations are received.
Properties
| Name | Meaning |
|---|---|
| Allow Unauthorized Certs (Legacy) | Whether to connect even if SSL certificate validation is not possible (hidden legacy option). |
| Poll Timespan | Legacy parameter for backward compatibility (hidden). |
| Request Options | Additional options to configure the request (activation-safe): |
| - Allow Unauthorized Certs | Whether to connect even if SSL certificate validation is not possible. |
| - Query Parameters | Query parameters to include in the request, provided as a JSON object string. |
| - Headers | Headers to include in the request, provided as a JSON object string. |
| Options | Legacy parameter for backward compatibility (hidden). |
| Additional Fields | Legacy parameter for backward compatibility (hidden). |
Output
The node outputs an array of items where each item corresponds to a confirmed donation event retrieved from the Charity's Purse API. Each output item has a json property containing:
id: The unique identifier of the donation.- All other properties returned by the API for the donation event, merged into the JSON object.
The output structure is essentially a list of donation objects with their full details as provided by the API.
Dependencies
- Requires an API key credential for the Charity's Purse API.
- The node makes authenticated HTTP GET requests to the Charity's Purse API endpoint
/v1/integrations/zapier/donation/donation/list. - Supports optional configuration of request headers and query parameters via the "Request Options" property.
- The node uses polling with a default interval of 60 seconds between requests.
Troubleshooting
Common issues:
- Invalid or missing API credentials will prevent successful authentication and data retrieval.
- Malformed JSON strings in "Query Parameters" or "Headers" fields will cause JSON parsing errors.
- Network or SSL certificate issues may occur; the node supports ignoring SSL validation if explicitly enabled.
- If no new confirmed donations are found, the node returns no output until new data arrives.
Error messages and resolutions:
- Errors related to authentication failure: Verify that the API key credential is correctly configured.
- JSON parse errors for query parameters or headers: Ensure valid JSON syntax is used in these fields.
- Request failures due to SSL issues: Enable "Allow Unauthorized Certs" if connecting to servers with self-signed certificates.
- Rate limiting or API errors: Check API usage limits and ensure the API endpoint is reachable.
Links and References
- Charity's Purse API documentation (if publicly available) — consult for detailed API endpoints and data schema.
- n8n documentation on creating and using trigger nodes.
- General REST API best practices for authentication and error handling.