Giving thank-you
When to use it
Section titled “When to use it”- Your giving platform or finance team can send Origamy an event for each gift (by API, a webhook relay or a CSV import).
- You want every gift acknowledged warmly and first-time givers welcomed personally.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| A webhook from another system | Your giving platform posts each gift to a webhook source. |
| A Google Sheet or Excel file, synced | Or finance keeps a giving sheet synced as events (one row per gift), or uploads a CSV each week. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Pastors | Thanks first-time givers personally. | Empty |
| Team | Finance | Gets the monthly giving summary. | Empty |
| Template | Thank you for giving (email) | The thank-you email (no amounts). | Ready |
| Question | Report: givers | How many people gave in the period. | Ready |
| Question | Report: first-time givers | How many gave for the first time. | Ready |
| Report | Monthly: giving summary | Givers and first-time givers last month, compared with the month before. No amounts. | Off |
| Follow-up | Giving: thank you | The thank-you email the morning after; at most once a week per giver. | Off |
| Follow-up | Giving: first-time giver | A first gift gives the pastoral team a task to thank the giver personally. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What should messages call your church? | none, must answer | org_name |
| 2 | What is the giving event called in your data? (one per gift) Its properties should include fund and method, and first_gift true on someone's first gift. The amount is never shown in messages. | Gift Received | gift_event |
| 3 | Who should personally thank first-time givers? | Pastors | pastoral_team |
| 4 | Who gets the monthly giving summary? | Finance | finance_team |
| 5 | Which address should thank-you emails come from? | none, must answer | email_from |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Thank-you after the gift | 12h | thanks_delay |
| Time zone for the report | ‹workspace timezone› | timezone |
| Greeting when a first name is missing | friend | greeting_fallback |
Timings
Section titled “Timings”- Thank-you email 12h after each gift, at most once a week per giver however often they give.
- First-time givers also create a task for Pastors to thank them personally, due in 3 days.
- Monthly summary on the 2nd at 09:00 (‹workspace timezone›): the number of givers and first-time givers, no amounts.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The thank-you | A verified sending domain for ‹Sender address›. |
What you need to do
Section titled “What you need to do”- Send Gift Received for each gift with properties fund, method and first_gift (true on a first gift), identified by the giver's email or phone. Don't put amounts in traits.
- Add people to the Pastors and Finance teams.
- Verify the sending domain, switch the follow-ups and report on, and test with your own gift record.
This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval) as a church workspace:
When someone gives, send them a warm thank-you the next morning, without mentioning the amount. If it's their first gift, ask one of the pastors to thank them personally. Send the finance team a monthly count of givers.
It passes when every piece is a valid draft and everything lands off, with at least: workflow, message_template. It must never use: discount, cart, checkout, purchase, revenue, customers, upsell.