Overview
This node triggers when a donation is abandoned on the CharitysPurse platform. It periodically polls the CharitysPurse API to check for donations with the status "abandoned" and emits these as output items. This trigger node is useful in workflows where you want to react to donors who started but did not complete their donation, enabling follow-up actions such as sending reminder emails or logging abandoned donations for analysis.
Practical examples:
- Automatically notify your team or CRM when a donation is abandoned.
- Trigger an email campaign encouraging donors to complete their donation.
- Log abandoned donations for reporting and improving donation processes.
Properties
| Name | Meaning |
|---|---|
| Allow Unauthorized Certs (Legacy) | Whether to connect even if SSL certificate validation is not possible (legacy hidden option). |
| Poll Timespan | Legacy parameter for backward compatibility (hidden). |
| Request Options | Additional options to configure the HTTP request safely during activation. Contains: |
| - Allow Unauthorized Certs | Whether to connect even if SSL certificate validation is not possible. |
| - Query Parameters | JSON string of query parameters to include in the request. |
| - Headers | JSON string of headers to include in the request. |
| Options | Legacy parameter for backward compatibility (hidden). |
| Additional Fields | Legacy parameter for backward compatibility (hidden). |
Output
The node outputs an array of items, each representing an abandoned donation. Each item contains a json object with the following structure:
id: The unique identifier of the donation.- All other fields returned by the CharitysPurse API for the donation are spread into the
jsonobject.
If no new abandoned donations are found since the last poll, the node returns null and does not emit any items.
The node does not output binary data.
Dependencies
- Requires an API key credential for the CharitysPurse API.
- The node makes authenticated GET requests to the CharitysPurse API endpoint
/v1/integrations/zapier/donation/donation/list. - Supports optional configuration of request headers and query parameters via the "Request Options" property.
- Uses internal n8n helper methods to handle authentication and HTTP requests.
Troubleshooting
- No output items: This usually means there are no new abandoned donations since the last poll or all have been processed already.
- Invalid JSON in Request Options: If the "Query Parameters" or "Headers" fields contain invalid JSON strings, the node will ignore them silently. Ensure valid JSON format.
- Authentication errors: If the API key is missing or invalid, the node will fail to authenticate and return no data. Verify that the API key credential is correctly configured.
- SSL certificate errors: If connecting to the API fails due to SSL issues, enable "Allow Unauthorized Certs" in the request options to bypass SSL validation (not recommended for production).
- Rate limiting or network errors: The node retries polling every 60 seconds; transient network issues may cause temporary failures. Check network connectivity and API limits.
Links and References
- CharitysPurse API documentation (not provided in code, please refer to official CharitysPurse resources)
- n8n HTTP Request node documentation for configuring request options and authentication
- General best practices for handling abandoned donations in fundraising platforms