Connectors

/

Chorus

/

Log Chorus donor emails to Bloomerang
Write
Cross-Connector

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.

Try PopdockAI free
Get a live demo
Log Chorus donor emails to Bloomerang
Log the emails jordan@contosofoundation.org sent us in the last 30 days to Bloomerang.
Jordan Lee sent 6 emails, and 3 need logging. - To log: Gala sponsorship question, 22 September - To log: Pledge schedule update, 29 September - Skipped: 2 private emails and 1 already logged Which purpose should I use, and shall I log the 3 emails?
Chorus
Sample figures. Your results come from your own account.
bloomerang-get-email-address
bloomerang-get-constituent
chorus-get-emails
bloomerang-get-interaction
bloomerang-add-interaction

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Chorus
Run it on your own Chorus data.

Connect Chorus, pick your AI tool and paste the prompt.

Try PopdockAI free

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.

Prompt
**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.

Your AI tool

02

Find

It finds the constituent in Bloomerang and the emails they sent through Chorus.

bloomerang-get-email-address
bloomerang-get-constituent
chorus-get-emails

03

Skip

It drops private emails and any already logged with the same subject that day.

bloomerang-get-interaction

04

Confirm

You choose a purpose and confirm before anything is logged.

Your AI tool

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.

get-data

bloomerang-get-email-address

Returns constituent email addresses from Bloomerang. Filter by address, type or primary flag, and include or exclude addresses flagged bad.
get-data

bloomerang-get-constituent

Returns constituents from Bloomerang: the donors, prospects and contacts in your database. Filter by full name, last name, account number, primary email, city, type or status, or fetch one by id.
get-data

chorus-get-emails

Returns emails captured by Chorus, including the subject, body, sender, owner, account and sent time. Filter by account or date range to read the written trail alongside the calls.
get-data

bloomerang-get-interaction

Returns logged interactions with constituents in Bloomerang: calls, emails, meetings and mailings. Filter by date range, channel, purpose or subject.
run-action

bloomerang-add-interaction

Logs an interaction with a Bloomerang constituent: a call, email, meeting or mailing, with its date, channel, purpose, direction and note.
Read only.Nothing in Chorus Changes

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.

How Popdock AI secures your data

The outcome

Donor emails on the record, private ones left out

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

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.

Try PopdockAI Free
See Documentation