/
/
Get donor emails onto Bloomerang records, without the private ones
For fundraising teams who want emails a donor sent, as captured by Chorus, logged as Bloomerang interactions, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Donor emails captured but never on the donor record
Donors write in by email and Chorus captures those messages, but Bloomerang only shows them if someone logs each one. Doing it by hand is tedious, and it is easy to log the same email twice or include a message marked private.
Without PopdockAI
- Find the donor in Bloomerang
- Read their emails in Chorus
- Leave out private messages by hand
- Check each one was not logged already
With PopdockAI
- The constituent is found, stopping if none or several match
- Private emails are skipped and counted
- Emails already logged that day with the same subject are dropped
- You choose one purpose and confirm before anything is logged
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Record the emails sent by `{donor-email}` in the last `{lookback-days}` days (default 30), as captured by Chorus, as inbound Email interactions on their Bloomerang constituent, skipping any already logged.
**Step 1: Find the constituent in Bloomerang**
Call `bloomerang-get-email-address` with `value` set to `{donor-email}` and take `account-id`. If nothing comes back, try `bloomerang-get-constituent` with `primary-email`. If there is still no match, say the donor is not in Bloomerang and stop. If more than one account matches, list them and stop.
**Step 2: Read the emails in Chorus**
Call `chorus-get-emails` with `initiator-email` set to `{donor-email}` and `sent-time.from` set to the start of the window. Skip emails where `private` is true and say how many were skipped. If none remain, say so and stop.
**Step 3: Skip what is already logged**
Call `bloomerang-get-interaction` with `account-id`, `channel` Email and `date.from` set to the start of the window. Treat a Chorus email as already logged if an interaction exists on the same calendar day with a subject matching its `name` (the email subject).
**Step 4: Confirm, then write**
Show a table: sent date, subject, Chorus owner (`owner-name`), action (log / already logged). For each row to log, the interaction will be: `date` the calendar day of `sent-time`, `channel` Email, `purpose` asked from the user once for the whole batch, `subject` the email subject, `is-inbound` true, `note` the first 500 characters of `body` followed by "Captured by Chorus, email {email-id}".
Ask the user to confirm. Only after an explicit yes, call `bloomerang-add-interaction` once per row to log. Report each returned `id`.
**Rules & Guidelines:**
* Tools whose names start with chorus are on the chorus server; tools whose names start with bloomerang are on the bloomerang server.
* The only write this prompt may make is `bloomerang-add-interaction`, and only after confirmation. Do not call `bloomerang-add-note`, `bloomerang-update-interaction`, `bloomerang-add-email-address` or any Chorus action.
* Never log a private email.
**Validation:**
* If `bloomerang-add-interaction` rejects the purpose value, report the error and ask for a valid one; do not guess.
* Match emails case-insensitively.Who it's for
One answer, three teams that use it
Major gift officers
Keep donor correspondence visible
Emails from your donors appear on their record, so colleagues see the full conversation.
Log the emails priya@contosofoundation.org sent us in the last 60 days to Bloomerang.
Development associates
Log emails without double entries
Emails already logged are dropped, so the record stays clean.
Log this month's emails from sam@fabrikam.org to Bloomerang, purpose Stewardship.
Database managers
Respect private messages
Private emails are never logged, and you are told how many were skipped.
Log Chorus emails from alex@northwindtraders.com since September to Bloomerang and tell me how many were private.
How it works
What PopdockAI does when you ask
You give the donor's email and a period, and your AI assistant prepares inbound email interactions in Bloomerang. A rejected purpose is asked about rather than guessed.
01
Ask
You give the donor's email and a look-back period.
02
Find
It finds the constituent in Bloomerang and the emails they sent through Chorus.
03
Skip
It drops private emails and any already logged with the same subject that day.
04
Confirm
You choose a purpose and confirm before anything is logged.
What PopdockAI provides
The tools behind the answer
Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.
bloomerang-get-email-address
bloomerang-get-constituent
chorus-get-emails
bloomerang-get-interaction
bloomerang-add-interaction
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Donor emails on the record, private ones left out
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
