Bloomerang automation · runs weekly
Prepare Bloomerang lapsed donor follow-up calls
Donors lapse quietly: no gift for 13 months, and nobody notices until the year-end report. A fundraiser filters the list, opens profiles one by one and decides who gets a call.
Cotlet does it in your own Bloomerang account with search_constituents, list_donations, list_interactions and create_task, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Bloomerang do this on its own?
Bloomerang filters lapsed donors in the dashboard, and Journey Automation can create a task and assign it to the relationship manager (checked 22 Oct 2026, changelog 16 Oct 2025). It sends the same task to every donor who matches. It does not read a donor's last gift and contact to decide who is worth a call this week, or write a task subject with that context.
How you do it in Bloomerang today
- Click Constituents, then Filter Results, and set Lifecycle Stage to Lapsed. The Analytics panel shows how many donors are Lapsed.
- Add more filters, such as Donor Types or Status Active, because Bloomerang lets you combine filters freely.
- Open each profile to read the latest transaction and the interactions on the timeline.
- Click the down arrow on the record and select New Interaction to log the call, with a Date, Subject, Purpose and Channel.
- Groups, then Add Group and Add Members, saves a list of lapsed donors for the team.
How to prepare Bloomerang lapsed donor follow-up calls
List Bloomerang donors who lapsed in the last 60 days with a gift of 100 or more. For each, read the last gift and the last interaction, and create a call task for Sam due next Friday. Skip anyone we contacted in the last 30 days. - 01
Pull the lapsed list
search_constituents runs with lifecycle_stage Lapsed and follows next_cursor to the end. The stage is Bloomerang's own: the latest transaction is older than 13 months.
- 02
Read the last gift
list_donations gives the gifts of each candidate. Donors below the amount in your prompt are dropped, and the date of the last gift goes into the task subject.
- 03
Skip recent contact
list_interactions with since set to 30 days back checks each donor. Anyone with a call, email or note in that window is skipped and listed, so nobody is called twice in a month.
- 04
Create the task
create_task assigns one call task per donor to the colleague you named, with a due date and a subject such as "Call about lapsed gift". notify stays false unless you ask, so the colleague gets one summary from the agent, not 20 emails.
- 05
Hand over the list
The agent returns who got a task, who was skipped and why. No email or message goes to any donor.
What you get back
Lapsed donors, gift of 100 or more, lapsed in the last 60 days: 9
Tasks created for Sam, due 2026-10-30: 6
- Lena Ortiz, last gift 150.00 on 2025-09-10
Skipped 3:
- Priya Nair: call logged 2026-10-08
- Hill Family Trust: note logged 2026-10-15 Other ways to ask
- Do the same for Recurring donors whose schedule ended, and assign the tasks to each donor's relationship manager.
- Only show me the list with last gift and last contact, and create no tasks.
- Every Monday, create tasks for newly lapsed donors with gifts of 500 or more.
What Bloomerang allows, and what to know first
- Bloomerang calls a donor Lapsed when the latest transaction is older than 13 months, and Current when there is one within the last 13 months.
- Donor types New, Retained, Recaptured and Recurring can be combined with the lifecycle stage, and Recurring counts active recurring schedules, not pledges.
- A user with restricted giving access can add interactions and tasks, but cannot select a giving-related purpose such as Solicitation.
- Users with No access to transactions still get task notification emails.
- Bloomerang's Journey Automation Create Task action can assign to the constituent's relationship manager, and uses the Assign To person if there is none.
create_task changes only your own Bloomerang data and reach no one else, so it runs without asking first.
Sources: Bloomerang Help: Constituent Dashboard · Bloomerang Help: User Permissions · Bloomerang Help: Add and Manage Constituent Groups and Members · Bloomerang Changelog
Call create_task from a script
curl -X POST https://cotlet.dev/api/v1/bloomerang/constituents/48211/tasks \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"user_id":12,"due_date":"2026-10-29","subject":"Call about lapsed gift","channel":"Phone"}' {
"id": 3318,
"constituent_id": 48211,
"user_id": 12,
"due_date": "2026-10-29",
"subject": "Call about lapsed gift",
"channel": "Phone",
"notified": false
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is bloomerang_write → create_task. Example data.
Schedule it in n8n, Make, Zapier or cronBloomerang tools this automation uses
| Tool | Parameters |
|---|---|
| search_constituents | query, type, status, lifecycle_stage, donor_type, cursor |
| list_donations | constituent_id, since, until, fund, cursor |
| list_interactions | constituent_id, purpose, channel, since, cursor |
| create_task | constituent_id, user_id, due_date, subject, channel, purpose, note, notify |
Frequently asked questions
Is it safe to connect Bloomerang to Cotlet?
Yes. You sign in to Bloomerang yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Bloomerang once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.
Give your agent access to Bloomerang.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Bloomerang.