> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/integrations/crm-donor-management/kindful.md). # Kindful Connect Anedot to Kindful to automatically sync donation and lead data, configure custom app credentials, and streamline donor management. > For the complete documentation index, see [llms.txt](https://anedot.gitbook.io/anedot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anedot.gitbook.io/anedot-docs/integrations/crm-donor-management/kindful.md). ## Kindful Connect Anedot to Kindful to automatically sync donation and lead data, configure custom app credentials, and streamline donor management. **Kindful** is a donor management and online giving platform designed for nonprofits. It helps streamline fundraising, donor tracking, communication, and reporting—empowering organizations to better understand donor behavior and improve fundraising strategies. > If you need assistance setting up the Kindful integration, please contact our [Support](https://www.anedot.com/getsupport) team. ### Connecting Anedot to Kindful Before connecting, complete the following steps in your **Kindful account**: 1. **Request Custom Apps Access** * Reach out to your Kindful representative to enable access. 2. **Log in to Kindful** * Navigate to **Apps → Custom Apps**. 3. Create a New Custom App * Name it **"Anedot"**. * *Optionally*, add a description. 4. **Generate a Security Token** * Click **Generate Security Token**. * If the button is not visible, click **Manage Credentials** to find it. Now, in your **Anedot account**: 1. Go to **Settings → Integrations → Directory**. 2. Click **+ New Connection** in the top-right corner. 3. Select **Kindful** from the list. 4. Choose the **Action Pages** you want to sync *(default is all)*. * To exclude pages, enter their IDs as a comma-separated list. 5. *(Optional)* Limit the sync to a specific **Team**. 6. Paste your **Kindful Security Token** into the API Token field. 7. Click **Save** to complete the connection. *You can update Action Pages, Team access, and credentials at any time.* ### Data Relays * Anedot sends data from both **Donation Pages** and **Lead Pages** to Kindful. * **Not supported:** * Transaction reversals *(e.g., voids, refunds)* * Relay of recurring donation frequency * **Push Unsent Support:** * You can push failed or past donations by specifying a date range. * This works across all Action Pages, regardless of type. ### Field Mapping | Anedot Field | Kindful Field | | ---------------------------------- | ----------------------------------------------------------------------------------------- | | data\_format (Kindful field) | event type {contact\_with\_transaction} (financial pages) {contact} (non-financial pages) | | action\_type (Kindful field) | action type | | match\_by: contact (Kindful field) | matching data through contact email (hardcoded) | | data\_type (Kindful field) | format for data coming through (json) | | first\_name | first name | | last\_name | last name | | email | email address | | primary phone | phone number | | company\_name | employer name | | addr1 | address line 1 | | addr2 | address line 2 | | city | city | | state | state | | postal | zip/postal code | | updated\_at | updated timestamp (in UTC, iso8601 format) | | amount\_in\_cents | transaction's total amount | | transaction\_id (submission ID) | transaction ID | | transaction\_type | transaction payment method type (e.g. credit card ) | | transaction\_updated\_at | transaction updated timestamp (in UTC, iso8601 format) | | campaign\_id (Action Page ID) | campaign ID | ### Payload Data #### Request Headers ``` { } ``` #### Request Body ```json {"data_format": "contact_with_transaction", "action_type": "update", "match_by": { "contact": "email" }, "data_type": "json", "data": [ { "first_name": "Annie", "last_name": "Dot", "email": "annie@anedot.com", "primary_phone": "12252501301", "company_name": null, "addr1": "1340 Poydras Street", "addr2": null, "city": "New Orleans", "state": "LA", "postal": "70112", "updated_at": "2024-06-21T03:16:31Z", "amount_in_cents": 2500, "transaction_id": "3f9eba14-76a3-4bc0-b72b-2e1a73cb34d0", "transaction_type": "credit_card", "transaction_updated_at": "2024-06-21T03:16:31Z", "campaign_id": "8a9467c6-1243-44d6-af68-2461a9975880" } ] } ``` #### Response Body *(Success)* ```json {"id": "f6c13ff5-130b-419d-8f73-40da5dcbf179", "status": "pending" } ``` #### Response Body *(Error)* ``` { } ``` #### Response Status *(Success)* ``` 200 ``` #### Response Status *(Failure)* ``` null ``` *** ## Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ### Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://anedot.gitbook.io/anedot-docs/integrations/crm-donor-management/kindful.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.anedot.com/integrations/crm-donor-management/kindful.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.