/
/
Warn fundraisers when a donor's email stops working
For fundraising operations teams who want Constant Contact bounces and unsubscribes noted on Bloomerang constituents, by asking their AI assistant.
On this page
Connector
Connect Constant Contact, pick your AI tool and paste the prompt.
The problem
Fundraisers rely on donor emails that stopped working
When a donor's email bounces or they unsubscribe in Constant Contact, fundraisers in Bloomerang keep relying on that address. Carrying the news across means matching each address to a constituent and noting it, without noting the same problem twice.
Without PopdockAI
- Export bounces and unsubscribes from Constant Contact
- Match each address to a constituent
- Check for an existing note
- Note the same problem twice, or miss it
With PopdockAI
- Bounces and unsubscribes are matched to Bloomerang by email
- Constituents already noted are skipped
- Temporary bounces are labelled so you can drop them
- You confirm the rows before any note is written
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find Constant Contact bounces and unsubscribes from the last {lookback-days} days (default 30), limited to the campaign {campaign} if one is given, and after the user confirms, add a note to each matching Bloomerang constituent so staff know the address has a problem.
**Step 1: Read the problems in Constant Contact**
If a campaign was given, call `constant-contact-get-campaign` with `name` (then `name.contains`) to get its campaign-id; if more than one matches, list them and stop. Then call `constant-contact-get-campaign-bounce` and `constant-contact-get-campaign-unsubscribe` with `created-date.from` set to today minus the lookback days, and `campaign-id` if you have one. Keep email-address, created-date, campaign-id, and bounce-type or reason.
**Step 2: Find each address in Bloomerang**
For each unique email, call `bloomerang-get-email-address` with `value` set to it. If nothing comes back, mark it Not in Bloomerang and skip it. Otherwise keep the account-id and whether Bloomerang already flags it bad.
**Step 3: Skip what is already noted**
For each account-id, call `bloomerang-get-note` with `account-id` and `date.from` set to the problem's created-date. If a note already mentions that email address and Constant Contact, skip it as Already noted.
**Step 4: Confirm**
Show the plan as a table: email, constituent account-id, problem (bounce type or unsubscribe), date, campaign-id, already flagged bad in Bloomerang. Label bounce types that look temporary (such as mailbox full) so the user can drop them. Ask the user to confirm all rows, a subset, or none. Write nothing until they reply.
**Step 5: Write the notes**
For each confirmed row, call `bloomerang-add-note` once with `account-id`, `date` set to the problem date as an ISO date, and `note` in this form: Constant Contact reported a hard bounce for jane@example.com on 2026-09-14 (campaign 1234). Use unsubscribe in place of the bounce wording for unsubscribes.
**Step 6: Report**
Counts of notes written, skipped (Not in Bloomerang, Already noted, declined) and failed, with the error for any failure.
**Rules & Guidelines:**
* Constant Contact tools: `constant-contact-get-campaign`, `constant-contact-get-campaign-bounce`, `constant-contact-get-campaign-unsubscribe`. Bloomerang tools: `bloomerang-get-email-address`, `bloomerang-get-note`, `bloomerang-add-note`.
* The only tool that writes is `bloomerang-add-note`, and only after the confirmation in Step 4.
* Do not call `bloomerang-update-email-address`, `bloomerang-update-constituent` or `constant-contact-update-contact`. The tools cannot set the Bloomerang bad flag; if the user wants it set, tell them to do it in Bloomerang.
* Match emails case-insensitively after trimming spaces. Never match on name alone.
* The Bloomerang constituent `id` is the same number every other Bloomerang tool takes as `account-id`.
**Validation:**
* If Constant Contact returns no bounces or unsubscribes, say so and stop.
* If one email belongs to more than one Bloomerang account, show every account in the plan and let the user choose.Who it's for
One answer, three teams that use it
Donor database managers
Keep donor contact data honest
Notes flag bad and opted-out addresses, and you are reminded to set the bad email flag yourself.
Note this quarter's Constant Contact hard bounces on the matching Bloomerang constituents.
Major gift officers
Know when to pick up the phone
A note on the donor tells you email is not getting through.
Which of our Bloomerang donors bounced in Constant Contact this month? Note them for me.
Development operations
Make bounce follow-up routine
Run it monthly and skip anything already noted.
Note the unsubscribes from our Year End Appeal campaign on the matching Bloomerang donors.
How it works
What PopdockAI does when you ask
You choose a look-back period and your AI assistant prepares notes for donors whose email bounced or opted out. Notes are written only after you confirm the rows.
01
Ask
You choose a look-back period, and optionally a campaign.
02
Match
It reads bounces and unsubscribes and matches each address in Bloomerang.
03
Skip
It skips constituents already noted and labels temporary bounces.
04
Confirm
You confirm all, some or none, then notes are written.
What PopdockAI provides
The tools behind the answer
Ready made tools for Constant Contact and one secure connection to your AI tool. No code, no exports.
constant-contact-get-campaign
constant-contact-get-campaign-bounce
constant-contact-get-campaign-unsubscribe
bloomerang-get-email-address
bloomerang-get-note
bloomerang-add-note
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
Email problems visible on the donor record
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)
