CharitysPurse Donation Initiated

Triggers when a donation is initiated
Join our community

Overview

This node triggers when a donation is initiated on the Charity's Purse platform. It periodically polls the Charity's Purse API to fetch new donation events that are either in "processing" or "confirmed" status but have not been previously processed by the node. This trigger node is useful for workflows that need to react automatically to incoming donations, such as sending thank-you emails, updating CRM systems, or logging donations for accounting purposes.

Practical examples:

  • Automatically send a personalized email to donors when their donation is confirmed.
  • Update a donor database or CRM with new donation details.
  • Trigger notifications or alerts within an organization when a new donation is 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 HTTP request safely during activation:
- 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 donation objects under the json field. Each output item corresponds to a single donation event and includes all properties returned by the Charity's Purse API for that donation, with the addition of an id field mapped from the internal _id.

Example structure of one output item:

{
  "json": {
    "id": "donation_unique_id",
    "status": "processing or confirmed",
    "created_at": "timestamp",
    "updated_at": "timestamp",
    "...other donation fields as returned by the API"
  }
}

No binary data is output by this node.

Dependencies

  • Requires access to the Charity's Purse API endpoint at https://api.charityspurse.ai/v1/integrations/zapier/donation/donation/list.
  • Optionally uses an API key credential for authenticated requests; if no credentials are provided, it makes unauthenticated requests.
  • Supports configuring additional HTTP request options such as custom headers and query parameters.
  • The node relies on n8n's polling mechanism and static workflow data storage to track processed donations and avoid duplicates.

Troubleshooting

  • Common issues:

    • Invalid JSON strings in "Query Parameters" or "Headers" will cause parsing errors; ensure these fields contain valid JSON.
    • If the API key or base URL is incorrect or missing, the node may fail to authenticate or connect.
    • Network issues or SSL certificate problems can be bypassed by enabling "Allow Unauthorized Certs," but this reduces security.
    • The node silently returns null to stop polling temporarily if the API request fails; check logs for underlying errors.

  • Error messages:

    • Errors related to JSON parsing of input fields: verify the JSON syntax in "Query Parameters" and "Headers".
    • Authentication errors: confirm that the API key credential is correctly configured.
    • Connection errors: consider enabling "Allow Unauthorized Certs" if SSL validation fails due to self-signed certificates.

Links and References

  • Charity's Purse API documentation (if publicly available) — check the official Charity's Purse developer site.
  • n8n documentation on creating trigger nodes and using polling mechanisms.
  • General REST API usage and authentication best practices.

Discussion