Salesforce Nonprofit Cloud Integration Question

Question

I have a question regarding the Salesforce integration with Klaviyo.

Previously, I successfully integrated Klaviyo with a Salesforce NPSP org using the standard Salesforce connector and authentication process, which required the Salesforce security token. However, I'm now trying to connect a Salesforce Nonprofit Cloud (NPC) org, and I've noticed that I can't find the option to reset or retrieve the Salesforce security token in this org.

I wanted to check whether Klaviyo currently supports integration with Salesforce Nonprofit Cloud, or if there are any additional configuration steps or prerequisites required for NPC that differ from NPSP.

Am I missing a configuration in the Salesforce NPC org, or is there a different authentication method recommended for Nonprofit Cloud?

I'd appreciate any guidance you can provide.

Temi O. · Accepted Answer

Hi there ​@Adil Abid Raja! From what I’m seeing, Klaviyo’s standard Salesforce CRM integration still expects the usual Salesforce authentication flow using a security token, and I’m not seeing separate Klaviyo documentation for Nonprofit Cloud specifically.My first thought is that this may be more of a Salesforce org configuration issue than an NPC-specific Klaviyo limitation. Salesforce notes that the “Reset My Security Token” option can be hidden for a few reasons, including profile login IP ranges, so it may be worth checking that with the Salesforce admin for the org.At least from my own research, I couldn’t find anything that says Klaviyo explicitly does not support Nonprofit Cloud, but I’m also not seeing a separate NPC authentication method documented either.Curious if anyone here has connected Klaviyo to a Salesforce Nonprofit Cloud org successfully, and whether it used the normal connector flow or required any extra setup.Temi@Klaviyo

tommethew · Answer

Salesforce Nonprofit Cloud supports API integrations, so the issue is usually related to the authentication method rather than the cloud edition itself. If you're not seeing the option to reset the security token, it's worth checking whether your organization is using IP restrictions, Single Sign-On, or OAuth policies that eliminate the need for a security token.

It may also be helpful to verify that the connected user has the required API permissions and that the integration user profile has access to the necessary objects and fields. If Klaviyo's connector relies on the legacy username, password, and security token flow, using OAuth with a connected app could be a more reliable approach if it's supported.

From a Salesforce consulting perspective, we've seen authentication settings differ between NPSP and Nonprofit Cloud deployments depending on the organization's security configuration, so reviewing those settings is often the first step before assuming it's a compatibility issue. Hopefully, someone from the Klaviyo team can confirm whether there are any Nonprofit Cloud-specific requirements.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials