Salesforce Classic
Connect Anedot to Salesforce Classic to sync donations and supporter data into your CRM workflows and related records from Settings → Integrations.
Salesforce Classic
A comprehensive guide for setting up, managing, and troubleshooting the Anedot integration with Salesforce Classic, including package installation, custom metadata, and field mapping.
Salesforce is a leading Customer Relationship Management (CRM) platform used by organizations to manage supporters, donations, processes, and communications.
Connecting Anedot to Salesforce requires a proper setup to ensure accurate and reliable data sync between the two systems. Because the process involves configuration and testing, we recommend completing the setup in both Anedot and Salesforce sandbox environments before going live.
To avoid impacting live data, all initial setup should be done in a sandbox environment.
Get Started
To begin, contact our Support team. We’ll create a sandbox account for your organization in Anedot. After successful testing, we’ll enable the Salesforce integration on your live account.
Before you begin, ensure your Salesforce user profile has the Download AppExchange Packages permission enabled.
Install The Anedot Package
Follow these steps to install the Anedot package in Salesforce:
Log in with your Salesforce credentials.
Add the following to the end of your URL:
/packaging/installPackage.apexp?p0=04t8Y000000ktYT&isdtp=p1Example URL:https://anedot.lightning.force.com/packaging/installPackage.apexp?p0=04t8Y000000ktYT&isdtp=p1You'll be redirected to the Package Installation Details page.
Review the package components.
Choose Install for All Users.
Click Install.
Note: This grants access to Salesforce APEX API. Approve third-party access by checking Yes, grant access to these third-party websites, then click Continue.
Wait for the installation to complete (a few minutes).
You’ll receive an email confirmation from Salesforce when installation is complete.
Configure The Anedot Package in Salesforce
Open the App Launcher in Salesforce.
Select Anedot.
Navigate to the Anedot Settings tab.
In the top-right, click New to create your Anedot Settings record.
Set your default values (e.g. Opportunity Stage).
Click Create when finished.
Copy the Webhook URL from the settings page—this will be used to complete the connection from Anedot.
Anedot Settings
Note: These defaults are based on a standard NPSP instance. If your organization has custom stages, statuses, or record types, you’ll need to adjust mappings accordingly.
Create GAU Allocation Records
Checkbox (default: checked)
Automatically create General Accounting Unit records.
Default Campaign Member Status
Dropdown (default: Planned)
Sets default status for campaign members.
Donation Amount Field
Dropdown (default: Total Donation Amount)
Sets which value to use as donation amount.
Integration Error Email
Text field
Email address to receive integration error alerts.
Opportunity Closed-Won Stage
Dropdown (default: Closed Won)
Default stage for successful opportunities.
Opportunity Open Stage
Dropdown (default: Prospecting)
Default stage for open (future) opportunities.
Update Contact Info from Anedot
Checkbox (default: checked)
Updates existing contacts using matched email.
Default Campaign
Campaign search
Assigns all records to one campaign instead of Action Page campaigns.
Default GAU
GAU search
Assigns all donations to one fund.
Opportunity Closed-Lost Stage
Dropdown (default: Closed Lost)
Used for failed or canceled donations.
Single Donation Record Type
Dropdown (default: NPSP Default)
Sets record type for single donations.
Webhook URL
Auto-generated
Use this to connect Salesforce in Anedot.
Source Object
Dropdown (NPSP or Salesforce)
Defines which Salesforce platform to map to.
Connect Anedot to Salesforce
Log in to Anedot.
Open the fundraising account you wish to connect.
Navigate to Settings → Integrations → Directory.
Click + New Connection.
Choose Salesforce from the list.
Enter your Salesforce Sub-Domain (e.g.
yournameif your domain isyourname.my.salesforce.com).(Optional) Add a Custom Field Mapping template.
Example Template:
Click Save.
You’ll be redirected to Salesforce to log in and authorize access.
Ensure the user connecting Anedot to Salesforce has Read, Write, and Edit access to the following objects:
Contacts
Opportunities
Campaigns & Campaign Members
GAU Allocations
Accounts
Once permissions are confirmed, the connection is complete!
Data Relays
Anedot automatically sends data from Donation and Lead Pages to Salesforce.
Action Pages are synced as Campaigns in Salesforce.
You can set a default Campaign for all submissions in Anedot Settings.
Example: If you receive donations from multiple vendors, you may want all submissions to be routed to a dedicated “Anedot” Campaign in Salesforce.

Reversed Transactions
Reversed or refunded transactions are logged as Anedot Donation Exceptions in Salesforce.
If a payload includes any of the following event labels, a record is created in the
Anedot_Donation_Exceptioncobject:commitment_failed_to_processdonation_chargeback_reverseddonation_partially_refundeddonation_refundeddonation_voided
Each exception record includes the event type, reversal amount, and a link to the related Salesforce Opportunity, if available.
Viewing Exceptions in Salesforce
Find all events in the Anedot Donation Exceptions tab within the Anedot app.
The related Opportunity record will also display linked exceptions under the "Related" → Anedot Donation Exceptions section.
Anedot does not automatically change the Opportunity stage for exceptions. For example, a voided donation will not be marked as
Closed–Lostunless you set that up via custom mapping in Salesforce.
Gift of Any Amount Products
To relay Gift of Any Amount products, you'll need to create a Custom Anedot Mapping using product fields from the submission_created event.
Custom Templates
Custom Templates allow you to relay custom data fields from Anedot to Salesforce. They can be used to:
Rename Anedot fields so they match Salesforce field names
Send organization-specific data directly to Custom Metadata fields in Salesforce
Creating a Custom Template
During Step 7 of the Connect Anedot to Salesforce process, you have the option to define or override field names using a Custom Template.
Example Template:
Next Steps in Salesforce
For each field in your Custom Template, create a Custom Metadata record in Salesforce.
After the metadata records are created, configure a corresponding Anedot Mapping in Salesforce to connect each field to its appropriate Salesforce object field.
This setup ensures your custom field data is relayed and processed correctly within Salesforce.
Continue below to learn how to create and configure Custom Metadata and Anedot Mappings.
Anedot Mapping and 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
Go to Setup → Custom Metadata Types in Salesforce.
Click Anedot Field.

Next, click Manage Anedot Fields.

Select New to create a custom mapping.

Fill in the following required fields:

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:
Open the Anedot Salesforce app.
Navigate to Anedot Mapping.
Select the Target Object (dropdown in upper right corner).

Click Create New Field Mapping.

Choose:
Event Type: (e.g.,
donation_completed)Attribute: (select from available custom metadata fields)
Salesforce Field: where the value should be stored.
Click Save.
You’ve now mapped a custom Anedot field to your Salesforce environment using Custom Metadata.
Field Mapping
The Anedot Fields match the Submission's Raw Data and the Salesforce Fields match the Request Body relay.
Submissions
submission_created
event
(Submission) id
id
phone
phone
title
title
suffix
suffix
referrer
referrer
utmCodes (term)
utm_term
paymentMethod (cardType)
card_type
(Donation) id
donations (id)
anedotFeeAmount (net amount in Entries)
fees (anedot_fee (amount))
vendorFeeAmount (net amount in Entries)
fees (vendor_fees (amount))
actionPagesFund (id)
fund (id)
actionPagesFund (name)
fund (name)
actionPagesFund (identifier)
fund (identifier)
netAmount (x100)
net_amount
grossAmount (x100)
gross_amount
feesPaidByDonor (TRUE/FALSE)
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
utmCodes (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)
product_name
utmCodes (campaign)
utm_campaign
employerName
employer_name
Product Value ( in dollars - Product)
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
donation_created or commitment created
event
created_at
date
firstName lastName
name
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))
vendorFeeAmount (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
address (line2)
address_line_2
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
action_page_updated or action_page_created
event
(Action Page) id
id
actionPage (name)
name
actionPagesFund (id name) "100"
funds (id name percentage)
Custom Field Created
custom_field_created
event
(custom field) id
id
Field Label
label
Custom Field Type
input_type
Internal Name
internal_name
Default Anedot Fields
donation_completed
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
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
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
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
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
Log in to Salesforce and go to Setup.
In the Quick Find bar, search for and select Users.
Select Users from the results.
Switch to Salesforce Classic view (if not already there).
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
Go to Setup in Salesforce.
In the Quick Find bar, search for Storage.
Click Storage Usage.
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?

