APIANT.ai / Stories / Church

Customer story · Church · Stripe and DonorPerfect

A church needed each Stripe gift in DonorPerfect, on the right donor, with its own codes. By the next day, its charges were arriving as gifts on their own.

A church takes recurring and one-off gifts online through Stripe and keeps its donor records in DonorPerfect. Its administrator described what was needed to the APIANT Assistant, and an hourly automation has been doing it since.

Apps in this story

The challenge

Gifts come in through Stripe, but the church's donor records are in DonorPerfect. Each paid charge had to become a gift on the right donor's record: found by email, then by name, with a new donor created only when neither matches, and every gift carrying the church's own codes.

The journey

  1. Day 1, afternoon

    The ask, then both apps connected

    The administrator asked the Assistant for Stripe charges to become DonorPerfect gifts, then connected both apps a minute apart.

  2. Day 1, late afternoon

    Tested on real charges

    The agent built the automation and tested it against three real Stripe charges the same afternoon.

  3. Day 2, late morning

    The church's own codes, then switched on

    Gifts in DonorPerfect carry the church's own codes. The agent looked up the church's own codes in DonorPerfect with a throwaway lookup, set them on every gift, and switched the automation on. The throwaway lookup was then deleted.

  4. Every hour since

    Charges in, gifts out

    Once an hour the automation picks up new Stripe charges. For each one it looks for the donor by email, then by name, and creates a donor only when neither finds one; then it adds the gift with the church's codes and the Stripe charge as the reference. In the most recent week, seven charges came in and seven gifts went out: five matched by email, one by name, one new donor.

    7 of 7

What they built

AutomationWhat it doesResult
Stripe charges to DonorPerfect giftsHourly: each new charge becomes a gift on the right donor record, with the church's codes, referenced to the charge241 runs, latest successful; 7 of 7 charges recorded in the past week

One automation. A first draft and a one-off code lookup were built along the way and deleted.

Why it worked

More stories

What would you ask for?

Start freeRead more stories

Details are taken from the account's own run history and shared without the church's name. No donor or gift details are included.