DonorAtlas for EveryAction — User Manual

1. Where Things Live

The integration lives on the Integrations page of DonorAtlas (Dashboard → Integrations). The EveryAction card there is the front door: it shows whether you are connected and links to Configure, Bulk sync, Users & connections and Auto-resync. In EveryAction itself there is nothing to open: DonorAtlas data appears in the custom contact fields your admin mapped and in a DonorAtlas note on the contact.

Who sees what:

2. Connecting Yourself

Your team connects to EveryAction once, with an API key an admin enters. After that, each member connects themselves with one click and no EveryAction sign-in.

• On the Integrations page, the EveryAction card says “You haven't connected your EveryAction account yet. Your team's API key is already set up, so connecting takes one click.” Click Connect your account.
• The card then reads “You're connected since Sep 18, 2026”.

3. Syncing One Donor from DonorAtlas

Open any donor's profile. The EveryAction button sits with the other actions.

• Sync (not yet synced): click it to open a picker. The usual choice is at the top: Match automatically. DonorAtlas checks your committee for this person by email, phone or address alongside the name: a confident match is linked and written, and no match creates a new contact. A contact that shares only the name is linked if the name is uncommon and no other contact has it; otherwise DonorAtlas creates a new contact and the job names the look-alike, so you can merge the two if they're the same person. To choose the contact yourself: EveryAction can't search people by name, so paste their VAN ID or EveryAction link, or give a first and last name (filled in from the donor) plus an email, a phone, or a street and ZIP code. Pick the contact and click Link selected. A contact already synced to another donor is greyed out.
• Syncing…: DonorAtlas is working. A second click does nothing until it finishes.
• View: the contact is synced. Click to open it in EveryAction in a new tab.
• The small arrow beside View opens two more actions for this one contact:Re-sync rewrites every mapped field from the latest research (needs the Sync permission), and Unsync… empties the mapped fields, clears the DonorAtlas note and drops the link, after a confirmation (needs the Unsync permission). Some of what DonorAtlas wrote stays on the contact (Section 6). Both run as jobs; the button reads Re-syncing… or Unsyncing… until they finish.
• Greyed out with “Your team hasn't allowed you to sync through EveryAction”: ask a team admin for the Sync permission (Section 8).

Errors show in a small red box under the button.

4. Sending a Whole DonorAtlas List

On Donor Lists, open a list's menu and choose Send to EveryAction. Each donor is checked against EveryAction first, so donors already there are linked rather than duplicated. The list runs as one job with a sub-job per donor; follow it in the jobs panel. You need the Bulk and Sync permissions.

5. Bulk Sync: Saved Lists

Integrations → EveryAction → Bulk sync (any team member; what you can run there depends on your Bulk, Sync and Unsync permissions). The table lists the saved lists that are shared with the user your API key belongs to, with Members, Synced and Last synced columns.

• Sync matches and writes every member that is not synced yet. One import credit is spent per newly matched contact.
• Re-sync rewrites every synced member with the latest DonorAtlas data. Free.
• Unsync… unsyncs every synced member, clearing the same things a single unsync does (team Admins with Bulk and Unsync only). A confirmation names the list. Free.
• Member counts are the ones EveryAction reports. Reading a saved list makes EveryAction export it, so DonorAtlas does not open one just to fill in the page; how much of a list is synced is known once a run over it has started.
• A running row turns blue and reads “Syncing 12 of 340…”. Progress also appears in the jobs panel.

How a run works: DonorAtlas asks EveryAction to export the list, waits until EveryAction says the file is ready, reads it, skips members already synced, and matches and writes the rest. Large lists take a while; EveryAction limits how fast an API key may call, and DonorAtlas waits out any throttling rather than dropping records.

Things you may see:

• A list you expect is missing: it is not shared with the API user. In EveryAction, share the list or its folder with that user, then click Refresh.
• “Your team is out of imports…” Buy more import credits, then try again.
• “That operation is already running for this list.” A run is in flight; wait for it to finish.
• “Bulk syncing is turned off for your account.” Ask a team admin for the Bulk and Sync permissions.

6. Configure: What DonorAtlas Writes

Integrations → EveryAction → Configure (Admin or Configure Only). This is where your team decides what lands where.

Single values

One row per DonorAtlas field (net worth range, giving capacity, gift figures, age, sex, religion, spouse, profile link, last synced date, political figures). Each dropdown offers the custom contact fields whose type can hold that value, or Not written. Figures go to Money or Number fields, text and the profile link to Text fields (EveryAction has no URL type), dates to Date fields. A field mapped to something EveryAction no longer has is flagged in amber and written nowhere until you re-map it. Each of your fields holds one DonorAtlas value, so a field another row already uses is shown with its name and can't be picked again. Fill in matches by name, above the list, ticks every value whose EveryAction field is named like it and points it there, leaving rows you have already set alone.

Repeating data (the DonorAtlas note)

EveryAction has nowhere structured to keep employment history and the like, so they are written as lines in one DonorAtlas note per contact. Keep Write a DonorAtlas note ticked and tick which of Employment, Education, Board Affiliations, Private Foundations, Public Donations and Social Media & Bio Websites to include. The note is rewritten on every sync and always opens with a link to the DonorAtlas profile.

What else a sync does

• Fill in employer, occupation and job title: writes the person's current employer, occupation and title into EveryAction's own fields. These follow the same rule as your mapped fields: DonorAtlas fills one that is empty, keeps updating one it filled, and leaves alone one someone on your team changed, unless you turn on the overwrite setting below, which covers these fields too. An unsync leaves them in place.
• Add social profiles to the person: puts the person's LinkedIn, Facebook, X (Twitter), Instagram and YouTube profiles into EveryAction's external ID slots for those networks, one per network, following the same rule. EveryAction has no way to remove an external ID, so these stay if you unsync.
• Stamp the DonorAtlas ID on the person (Advanced): adds each person's DonorAtlas id to their record as a “DonorAtlas” external ID. EveryAction accepts only external ID types your committee already has, and only EveryAction's support team can create one, so you ask them to add one named DonorAtlas first (the steps are in the technical documentation). The configuration page checks your committee and says whether the type is there; until it is, the switch can't be turned on. Nothing in DonorAtlas reads the stamp back.

Verified contact information

One checkbox covering Mailing Address, Verified Personal Email and Verified Mobile Phone. When on, each sync appends DonorAtlas's verified email and mobile phone to the contact's emails and phones. EveryAction cannot remove an email or phone once added, so unsyncing leaves them in place. That is why it is off by default. The mailing address is not added to contacts you already have: it is written only when DonorAtlas creates a new contact for a donor you send, and then whether or not this box is ticked.

Political data

If your team has turned political data off for EveryAction, the political rows are not offered here and any earlier mapping is kept dormant. An admin changes that under Political Data on the profile page.

Click Save configuration. “Saved. DonorAtlas will write these fields from now on.” confirms it. Changing the mapping does not rewrite already-synced contacts by itself; run a Re-sync (or wait for the nightly refresh) to apply it.

Values your team typed are safe. DonorAtlas fills a mapped field when it is empty and keeps updating values it wrote itself. If someone changes a value in EveryAction, DonorAtlas leaves it alone from then on and the job says which fields it left. If your mapped fields are for DonorAtlas only, tick Let DonorAtlas overwrite values already in these fields under “What else a sync does”. With it on, DonorAtlas also writes over employer, occupation, job title and social profiles when you have those switched on.

What an unsync leaves behind. An unsync empties the mapped fields that still hold what DonorAtlas wrote and replaces the DonorAtlas note's text with a line saying the data was removed. EveryAction offers no way to delete a note or to remove an email, a phone, an address or an external ID, so the note itself, verified emails and phones, the mailing address on a contact DonorAtlas created, social profiles and the DonorAtlas ID stamp all stay. Employer, occupation and job title stay too.

7. Replacing the API Key

If EveryAction stops accepting the key (it expired or was revoked), everyone connected to EveryAction sees a pop-up: “Your team's EveryAction API key is no longer accepted, so syncing and sending donors to EveryAction will fail until it is updated.” Admins and Configure Only users get an Update API key button that lands on the Configure page with the key box focused.

Paste the new key, including its |1 suffix, and click Save key. Only the key changes: your field mapping stays exactly as it is and every member keeps their connection. The new key must belong to the same committee.

8. Users & Connections and Permissions

Integrations → Users & connections (Admin or Configure Only) lists everyone connected to EveryAction and what each may do:

Every connected member can see synced profiles whatever their permissions; a member with none of the three is view-only. Members have full access until you restrict them. Remove connection disconnects a member and clears their permissions; if they reconnect they are view-only until you grant more.

The Inviting someone to connect card holds paste-ready instructions, with a Copy button, to send a new team member.

9. Auto-resync

Integrations → EveryAction → Auto-resync. Every night DonorAtlas finds synced contacts whose data is due for a refresh and re-syncs them the same way a manual Re-sync does: DonorAtlas data on the contact is replaced with the newest research, and your own EveryAction fields are never touched. The page shows the cadence (default every 7 days) and the next scheduled run; Edit settings changes the cadence. A team with a bulk run in progress is skipped that night.

10. Disconnecting

The Uninstall card on Configure (Admin or Configure Only) clears DonorAtlas data from every contact the team has synced (mapped fields emptied, the DonorAtlas note replaced with a line saying the data was removed; what an unsync leaves behind stays, as described in Section 6), then disconnects EveryAction and deletes the team's key and every member's connection. It runs as a job; a team with many synced contacts can leave it running and follow it in the jobs panel. The contacts and your custom fields stay in EveryAction. Reconnecting later means entering a key and mapping the fields again.

11. Credits

An import credit is spent once per contact, when it is first matched in a bulk sync. Sending a donor from DonorAtlas, re-syncing, unsyncing and the nightly refresh spend nothing. A contact that could not be matched is remembered, so a later bulk sync does not pay for it again.

12. Frequently Asked Questions

Where do I get an EveryAction API key?

From the sidebar, API Integrations → Request an API Key, naming DonorAtlas; an administrator approves it; then API Integrations → Generate API Key. Paste it into DonorAtlas exactly as shown, ending in |1.

Why does my key end in |1?

EveryAction keys carry a database suffix. |1 points the key at My Campaign, the CRM side, which is where DonorAtlas writes.

Why is a field missing from the dropdown?

Only fields whose type can hold the value are offered. Dollar figures need Money or Number, counts Number, text and links Text, dates Date.

Why is my saved list not listed?

Saved lists belong to the user who saved them. Share the list, or its folder, with the user your API key belongs to.

Does DonorAtlas change contributions, codes or names?

No. It writes only to the custom fields you mapped and the DonorAtlas note, plus whatever you switched on: employer, occupation and job title, social profiles, the DonorAtlas ID stamp, and verified email and phone. A contact DonorAtlas creates for a donor you send also gets the donor's name and mailing address.