For the complete documentation index, see llms.txt. This page is also available as Markdown.

Salesforce NPSP

Connect Anedot to Salesforce NPSP to sync donations and supporter data into your CRM workflows and related records via Settings → Integrations.

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Salesforce NPSP

A step-by-step guide to setting up, configuring, and troubleshooting the Salesforce NPSP integration with Anedot for seamless nonprofit fundraising data management.

Salesforce is a Customer Relationship Management (CRM) platform used by organizations to manage supporter relationships, sales, marketing, and communications.

Connecting Anedot (or other third-party platforms) to Salesforce involves a thorough setup process, including configuration, customization, and testing to ensure reliable data flow and performance.

To avoid affecting live data during setup, Anedot requires all integrations to be tested in a Salesforce and Anedot Sandbox environment first.

Getting Started

  1. Contact our Support team to request an Anedot Sandbox account.

  2. Test and confirm your configuration in the Sandbox.

  3. Once successful, we’ll enable Salesforce integration for your live account.

Before beginning, ensure your Salesforce user profile has the Download AppExchange Packages permission enabled. This is required to install necessary components.

Install The NPSP Package

To begin, you’ll need to install the Nonprofit Success Pack (NPSP) in your Salesforce account.

Note: If NPSP is already installed, you can skip this step.

Steps to Install NPSP:

  1. Log in to your Salesforce account and go to the AppExchange.

  2. Search for Nonprofit Success Pack.

  3. Click Get It Now on the package listing.

  4. Log in to the AppExchange using your Salesforce credentials.

  5. Choose where to install the package:

    • Install in Production or

    • Install in Sandbox

  6. Select the users for whom you want to install NPSP.

  7. Click Install.

  8. If prompted, approve third-party access by checking Yes, grant access to these third-party websites, then click Continue.

  9. The installation will start. You’ll receive an email confirmation once it’s complete.

After receiving confirmation that the NPSP package is installed, you can proceed to install the Anedot Package.

Install The Anedot Package

To install the Anedot Package in Salesforce, follow these steps:

  1. Log in using your Salesforce credentials.

  2. Add the following to the end of your URL: /packaging/installPackage.apexp?p0=04t8Y000000ktYT&isdtp=p1 Example URL: https://anedot.lightning.force.com/packaging/installPackage.apexp?p0=04t8Y000000ktYT&isdtp=p1

  3. You’ll be redirected to the Package Installation Details page.

  4. Review the package components.

  5. When prompted, choose Install for All Users.

  6. Click Install.

  7. Note: This grants access to the Salesforce APEX API. If asked to approve third-party access, check Yes, grant access to these third-party websites, then click Continue.

  8. Wait for the installation to complete (this may take a few minutes).

  9. You’ll receive an email confirmation from Salesforce once installation is successful.

After installation, you can proceed to configure the Anedot Package in Salesforce.

Set Up the Anedot Package in Salesforce

To configure the Anedot Package in Salesforce, follow these steps:

  1. Open the App Launcher in Salesforce (look for the grid icon below your organization’s logo).

  2. Select Anedot from the available apps.

  3. Go to the Anedot Settings tab.

  4. In the top-right corner, click New to create a new Anedot Settings record.

  5. Configure your default settings._These may vary based on your organization’s Salesforce setup._Make sure to define your Opportunity Stage defaults.

  6. Click Create once your settings are in place.

  7. On the Anedot Settings screen, copy the Webhook URL.This subdomain is required to connect Anedot to Salesforce. Refer to Step 6 in the next section for use.

You’re now ready to return to Anedot and complete the integration with your Salesforce account.

Anedot Settings

The chart is a list of the Anedot Settings we currently provide:

Anedot Setting Field
Options
Notes

Create GAU Allocation Records

Checkbox(default: checked )

When enabled, creates GAU (General Account Unit) Allocation Records.

Default Campaign Member Status*

Dropdown (default: Planned )

Status Campaign Members (page submitters) default to.

Donation Amount Field

Dropdown (default: Total Donation Amount )

Default amount used to track donations.

Integration Error Email Address

text input for email (default: Salesforce admin email ).

Email that receives notices of errors with the integration.

Opportunity Closed-Won Stage*

Dropdown (default: Closed Won )

Default opportunity stage for successfully relayed submissions.

Opportunity Open Stage*

Dropdown (default: Prospecting )

Stage open opportunities (e.g. future opportunities for commitments) default to.

Update Contact Info from Anedot

Checkbox(default: checked )

Update existing contacts with Anedot data (based on email matching).

Default Campaign*

Campaign search field (default: none )

Relayed submissions (opportunities, contacts, etc) are linked to a default campaign instead of Action Page specific campaigns.

Default GAU*

General Account Units (GAU) search field (default: none )

Relayed donations are always linked to the same GAU (fund) instead of the Anedot/relayed fund.

Opportunity Closed-Lost Stage*

Closed Lost

Default opportunity stage for lost opportunities (used for future opportunities linked to canceled commitments).

Single Donation Record Type

Dropdown (default: NPSP Default )

Default record type for new relays.

URL for webhook

Instance-specific

Instance-specific URL, used for the Salesforce URL when configuring the Salesforce integration in Anedot.

Source Object

Dropdown (default: None )

Salesforce application we are mapping objects for (options - NPSP, Salesforce). For customers using NPSP, they should select NPSP; for those using Salesforce CRM, they should use Salesforce

* The instructions above are based on a standard, uncustomized NPSP (Nonprofit Success Pack) instance. Certain object-specific settings—such as Campaign Member Status or Opportunity Stage—may differ depending on how your Salesforce environment has been customized.

By default, Anedot maps to standard NPSP/Salesforce fields (e.g., status, stage) when those fields are available. If your organization uses custom values or alternative configurations, it is your responsibility to update and map those settings accordingly to ensure proper data handling.

Connect Anedot to Salesforce

Follow the steps below to link your Anedot fundraising account with Salesforce:

1. Set Up the Integration in Anedot

  1. Log in to your Anedot account.

  2. Navigate to the fundraising account you want to connect to Salesforce.

  3. From the main menu, go to: Settings → Integrations → Directory

  4. Click the + New Connection button in the upper-right corner.

  5. In the Integration Directory, choose Salesforce.

  6. Enter the Sub-Domain URL of your Salesforce instance. For example, if your instance is anedot.my.salesforce.com, enter anedot (exclude https://).

  7. (Optional) Add a template for Custom Field Mapping in the Metadata field.

    1. Example:

  1. Click Save.

2. Authorize the Connection in Salesforce

  1. You’ll be redirected to log in to your Salesforce account.

  2. Upon login, grant Anedot access to required permissions by clicking Allow.

**Important:**The user connecting the integration must have appropriate permissions in Salesforce to enable data relay successfully.

3. Required Salesforce Permissions

The connecting user must have Read, Write, and Edit access to:

  • Recurring Donations (NPSP only)

  • Contacts (NPSP, Classic Salesforce)

  • Opportunities (NPSP, Classic Salesforce)

  • Campaigns & Campaign Members (NPSP, Classic Salesforce)

  • GAU Allocations (NPSP, Classic Salesforce)

  • Accounts (NPSP, Classic Salesforce)

Once access is granted and permissions are confirmed, your integration setup is complete!

Data Relays

Anedot automatically syncs data from Donations and Lead Pages into Salesforce. Here’s how key data elements are handled:

Campaigns

  • All Action Pages are converted into Campaigns in Salesforce.

  • A default Campaign can be set under Anedot Settings.

    • Useful for grouping data by initiative or vendor (e.g., all Facebook donations under one Campaign).

    • _Example: Set the default campaign field in Anedot Settings to Anedot.

Salesforce — Campaigns with default Campaign from Anedot Settings

_

Funds / GAUs

  • In NPSP, funds are mapped to General Accounting Units (GAUs).

  • By default, Anedot will create or update GAUs for each fund submitted.

  • GAU creation can be disabled, or a default GAU can be set in Anedot Settings.

    • _Example: To send all donations to “General Fund,” set this as the default GAU in Anedot Settings → General Fund.

Salesforce NPSP — General Accounting Units (GAUs)

_

Contacts

  • Contacts are created/linked from Action Page submissions.

  • Matching is done using email or phone number (based on NPSP Contact Matching rules).

  • Campaign Member records are also created and linked.

    • Can be customized in Anedot Settings.

Salesforce NPSP — Household Account Contacts and Opportunities

Donations

  • One-time donations are logged as Closed-Won Opportunities.

Salesforce NPSP — One-time donation Opportunity

With Commitment Events Enabled

  • Recurring donations create:

    • A Recurring Donation object.

    • Open Opportunities for future payments.

  • Commitment updates (e.g., amount, frequency) sync to both Recurring Donation and Opportunity records.

  • Canceled/deactivated commitments will update all remaining open (future) Opportunity records as "Closed Lost" and close all Recurring Donation records.

  • If a commitment ends or fails, the Recurring Donation is marked as "Fixed," and the Open Ended Status field is set to "None."

Salesforce NPSP — Recurring Donation with Commitment Events enabled

Without Commitment Events

  • Recurring donations are logged as individual Opportunities, similar to one-time donations.

Submissions

  • Requires NPSP. Anedot matches Submissions to Salesforce Contact records by email (or NPSP settings).

Salesforce NPSP — Submissions matched to Contacts

Reversed Transactions

  • Reversals (refunds, chargebacks, voids) are logged as Anedot Donation Exceptions.

  • Common event labels that trigger exceptions:

    • commitment_failed_to_process

    • donation_chargeback_reversed

    • donation_partially_refunded

    • donation_refunded

    • donation_voided

  • Exceptions are shown in the Anedot Donation Exceptions tab and linked to the related Opportunity in Salesforce.

Salesforce will not auto-update Opportunity stage when a donation is reversed.

Gift of Any Amount Products

  • To relay “Gift of Any Amount” products, use a custom Anedot mapping.

  • Reference the submission_created event and use Salesforce product fields as needed.

Custom Templates

Custom Templates allow you to relay specific or renamed Anedot data fields into Salesforce. You can use these templates to:

  • Rename Anedot fields to match your Salesforce field names.

  • Map unique data points directly to Salesforce Custom Metadata fields.

How to Create a Custom Template

You can create a Custom Template during Step 7 of the Connect Anedot to Salesforce process by entering a custom field mapping.

  • Example:

  • Template Field Notes:

    • close_date: Your custom Salesforce field for close dates.

    • donation_method: Custom constant (e.g., credit card).

    • action_page_id: Overrides Anedot’s default action page ID.

    • stage: Custom Salesforce Opportunity stage.

    • prefix: Maps to a Salesforce-specific custom field.

Anedot Mapping & Custom Metadata

Use Anedot Mapping and Custom Metadata to configure how Anedot fields are relayed to Salesforce—especially fields not included in the default mappings. This enables you to:

  • Map Anedot fields to custom Salesforce fields

  • Extend your integration to support organization-specific data requirements

Default Anedot Fields are included automatically in Custom Metadata when the Anedot Package is installed.

Note: If you are only mapping Default Anedot Fields, you can skip this section and go straight to Set Up Anedot Mapping. Custom Metadata is only required if you need to map additional fields not included by default.

To customize mappings beyond the default setup, you’ll need to create an Anedot Mapping within the Anedot Salesforce application. This allows you to define how Anedot relay fields (based on Event Type) connect to Salesforce fields (based on Object Type).

If a field is present in the Anedot payload but not supported by default, custom mapping is required to ensure Salesforce can interpret and process the data correctly. This step is essential for users implementing Custom Templates.

Event Type: donation_completed, commitment_created, submission_created, action_page_created, and action_page_updated

Object Type: Contact, Opportunity, Recurring Donation, Campaign Member

Create Custom Metadata in Salesforce

  1. Go to Setup → Custom Metadata Types in Salesforce.

  2. Click Anedot Field.

Salesforce Setup — Custom Metadata Types Anedot Field
  1. Next, click Manage Anedot Fields.

Salesforce Setup — Manage Anedot Fields
  1. Select New to create a custom mapping.

Salesforce Setup — New Anedot Field custom mapping
  1. Fill in the following required fields:

Salesforce Setup — Anedot Field required fields form
  • Label: Friendly name (e.g., custom_prefix_label)

  • Field Name: API-compliant name (e.g., custom_prefix)

  • Data Type: Type of field (Text, Number, etc.)

  • Event Type: Target event (e.g., donation_completed, commitment_created, submission_created, commitment_updated, action_page_created, action_page_updated)

  • Path: Dot-notation path to the value in the payload (e.g., payload.prefix). May be suggested after selecting Event Type, but confirm or adjust as needed.

Set Up Anedot Mapping

After defining your custom fields:

  1. Open the Anedot Salesforce app.

  2. Navigate to Anedot Mapping.

  3. Select the Target Object (dropdown in upper right corner).

Anedot Mapping — select Target Object
  1. Click Create New Field Mapping.

Anedot Mapping — Create New Field Mapping
  1. Choose:

    • Event Type: (e.g., donation_completed)

    • Attribute: (select from available custom metadata fields)

    • Salesforce Field: where the value should be stored.

  2. Click Save.

You’ve now mapped a custom Anedot field to your Salesforce environment using Custom Metadata.

Field Mapping

Submission

The Anedot Fields match the Submission's Raw Data and the Salesforce Fields match the Request Body relay.

Anedot Field
Salesforce Field

submission_created

event

(Submission) id

id

email

email

phone

phone

title

title

suffix

suffix

referrer

referrer

utmCodes term

utm_term

paymentMethod cardType

card_type

(Donation) id

donation (id)

anedotFeeAmount (net amount in Entries)

fees (anedot_fees (amount))

vendorFeeAmount (net amount in Entries)

fees (vendor_fees (amount))

actionPagesFund (id)

fund (id)

actionPagesFund (name)

fund (name)

actionPagesFund (identifier)

fund (identifier)

netAmount (x100)

donations (net_amount)

grossAmount (x100)

donations (gross_amount)

feesPaidByDonor (TRUE/FALSE)

donations (fees_paid_by_donor)

lastName

last_name

created_at

created_at

firstName

first_name

ipAddress

ip_address

occupation

occupation

(Product) id

product_id

updatedAt

updated_at

utmCodes (medium)

utm_medium

utmSource (source)

utm_source

account (id)

account_uid

middleName

middle_name

sourceCode

source_code

utmCodes (content)

utm_content

account (name)

account_name

address (city)

address_city

Internal SKU (Product)

product_code

Product Name

product_name

utmCodes (campaign)

utm_campaign

employerName

employer_name

Product Value (in dollars)

product_value

(Action Page) id

action_page_id

address (line1)

address_line_1

address (line2)

address_line_2

address region

address_region

address country

address_country

paymentMethod (cardMonth) / paymentMethod (cardYear)

card_expiration

donations (amount) (x100)

donation_amount

actionPage (name)

action_page_name

paymentMethod (lastDigits)

card_last_digits

donorProfileId

donor_profile_id

""

referrer_to_form

paymentRequests (responseTime)

created_at_iso8601

currentlyEmployed (TRUE/FALSE)

currently_employed

updatedAt

updated_at_iso8601

address postalCode

address_postal_code

paymentMethod (type)

payment_method_type

customFieldResponses (multiple fields)

custom_field_responses

communicationsConsentEmail

communications_consent_email

communicationsConsentPhone

communications_consent_phone

Donation/Commitment

The Anedot Fields match the Submission's Raw Data and the Salesforce Fields match the Request Body relay.

Anedot Field
Salesforce Field

donation_created or commitment_created

event

created_at

date

firstName lastName

name

email

email

phone

phone

title

title

hosted

origin

paymentMethod (type)

source

completed

status

suffix

suffix

(Donation) id

donations (id)

anedotFeeAmount (net amount in Entries)

fees (anedot_fees (amount))

vendorFeesAmount (net amount in Entries)

fees (vendor_fees)

actionPagesFund (id)

fund (id)

actionPagesFund (name)

fund (name)

actionPagesFund (identifier)

fund (identifier)

paymentMethod (cardType)

card_type

paymentMethod (lastDigits)

card_last_digits

paymentMethod (cardMonth) paymentMethod (cardYear)

credit_card_expiration

referrer

referrer

frequency

frequency

lastName

last_name

recurring (TRUE/FALSE)

recurring

created_at

created_at

firstName

first_name

ipAddress

ip_address

netAmount (x100)

net_amount

occupation

occupation

updatedAt

updated_at

account (id)

account_uid

middleName

middle_name

sourceCode

source_code

account (name)

account_name

address (city)

address_city

""

check_number

created_at

date_iso8601

grossAmount (x100)

event_amount

""

organization

employerName

employer_name

(Submission) id

submission_id

(Action Page) id

action_page_id

address (line1)

address_line_1 (appears as line 1 of Billing Address)

address (line2)

address_line_2 (appears as line 1 of Billing Address)

address (region)

address_region

(Commitment) id

commitment_uid

address (country)

address_country

actionPage (name)

action_page_name

"1"

commitment_index

donorProfileId

donor_profile_id

""

referrer_to_form

totalAmount (x100)

amount_in_dollars

donations (paymentMethodId)

payment_method_id

paymentRequests (responseTime)

created_at_iso8601

currentlyEmployed (TRUE/FALSE)

currently_employed

updatedAt

updated_at_iso8601

address (postalCode)

address_postal_code

Payment Method

payment_description

customFieldResponses (multiple fields)

custom_field_responses

recurring (TRUE/FALSE)

is_recurring_commitment

(Commitment) schedule_until

commitment_recurring_until

communicationsConsentEmail

communications_consent_email

communicationsConsentPhone

communications_consent_phone

Action Page Events

The Anedot Fields match the Submission's Raw Data and the Salesforce Fields match the Request Body relay.

Anedot Field
Salesforce Field

action_page_updated or action_page_created

event

(Action Page) id

id

actionPage (name)

name

actionPagesFund (id)

funds (id)

actionPagesFund (name)

funds (name)

actionPagesFund "100"

funds (percentage)

Custom Field Created

The Anedot Fields match the custom field in the Form Preset and the Salesforce Fields match the Request Body relay.

Anedot Field
Salesforce Field

custom_field_created

event

Field Label

label

Custom Field Type (Birthday, Date, Selection List, Hidden Question, Text, Requirement)

input_type

Internal Name

internal_name

Default Anedot Fields

donation_completed

Available Field
Field Type

payload.account_name

text

payload.account_uid

text

payload.action_page_id

text

payload.action_page_name

text

payload.address_city

text

payload.address_country

text

payload.address_line_1

text

payload.address_line_2

text

payload.address_postal_code

text

payload.address_region

text

payload.amount_in_dollars

number

payload.commitment_uid

text

payload.communications_consent_email

boolean

payload.communications_consent_phone

boolean

payload.created_at

datetime

payload.created_at_iso8601

datetime

payload.currently_employed

boolean

payload.donation.credit_card_expiration

text

payload.donation.card_last_digits

number

payload.donation.card_type

text

payload.donor_profile_id

text

payload.email

email

payload.employer_name

text

payload.event_amount

number

payload.first_name

text

payload.ip_address

text

payload.is_recurring_commitment

boolean

payload.last_name

text

payload.middle_name

text

payload.net_amount

number

payload.occupation

text

payload.origin

text

payload.payment_method_id

text

payload.phone

phone

payload.recurring

boolean

payload.referrer

text

payload.referrer_to_form

text

payload.source_code

text

payload.submission_id

text

payload.suffix

text

payload.title

text

payload.updated_at

datetime

payload.updated_at_iso8601

datetime

commitment_created

Available Field
Field Type

payload.action_page_id

text

payload.action_page_name

text

payload.address_city

text

payload.address_country

text

payload.address_line_1

text

payload.address_line_2

text

payload.address_postal_code

text

payload.address_region

text

payload.cancellation_reason

text

payload.cancelled_on

datetime

payload.cancelled_on_iso8601

datetime

payload.communications_consent_email

boolean

payload.communications_consent_phone

boolean

payload.created_at

datetime

payload.created_at_iso8601

datetime

payload.currently_employed

boolean

payload.donor_profile_id

text

payload.email

email

payload.employer_name

text

payload.first_name

text

payload.frequency

text

payload.id

text

payload.ip_address

text

payload.last_name

text

payload.middle_name

text

payload.next_capture_on

datetime

payload.occupation

text

payload.payment_method_id

text

payload.payment_status_message

text

payload.phone

phone

payload.referrer

text

payload.referrer_to_form

text

payload.submission_id

text

payload.suffix

text

payload.token

text

payload.total_amount_in_dollars

text

payload.updated_at

datetime

payload.whodunnit

text

action_page_created and action_page_updated

Available Field
Field Type

payload.id

text

payload.name

text

Payload Examples

Request Headers

Submissions

Donations

Commitments

Action Page Events

Custom Field Created

Failure

Troubleshooting

If you're seeing Auth Failure errors in Anedot, such as the one below, you may need to review your Salesforce Login History to determine the cause:

How to Check Salesforce Login History

  1. Log in to Salesforce and go to Setup.

  2. In the Quick Find bar, search for and select Users.

  3. Select Users from the results.

  4. Switch to Salesforce Classic view (if not already there).

  5. Under the selected user, open the Login History tab.

    • Look for:

      • "Username-Password Flow Disabled" → You'll need to enable OAuth Username-Password Flows.

      • "Password Lockout" → Wait for the lockout period to end or reset the password.

If Data Is Not Relaying to Salesforce

If relays appear successful in Anedot but are not arriving in Salesforce, the issue may be related to your Salesforce Storage Limits.

How to Check Storage Usage

  1. Go to Setup in Salesforce.

  2. In the Quick Find bar, search for Storage.

  3. Click Storage Usage.

  4. Review your usage:

    • If storage exceeds 60%, this may prevent relays from being accepted.

    • To resolve, delete older or unnecessary records to free up space.


Was this helpful?