Not able to see all Salesforce NonProfit Cloud objects

Hi there @FosterFamily,

Welcome to the Community! 🎉

I did some digging into this, and it seems like the Salesforce integration doesn’t support all of the non-profit cloud objects. It looks like our Support Team has already added your vote to the open feature request to support all of the non-profit cloud objects.

In the meantime, you can explore API Request (Beta) as a workaround as long as the Salesforce API supports it. Please note that, the API Request (Beta) is considered an advanced feature, so our support for it may be more limited. Not because we don't want to help, but because APIs can be tricky to troubleshoot since we can't see what's happening on the other side. Every API that you send a request to is going to have slightly different structures that are required.

This makes it hard for us to know why the request may be receiving errors or not working as expected, beyond taking a general look at what's showing in Zapier.

Here are some helpful resources:

• Make raw HTTP requests with API Request actions (Beta): https://help.zapier.com/hc/en-us/articles/14096700504717-Make-raw-HTTP-requests-with-API-Request-actions-Beta-
• Set up an API request action: https://help.zapier.com/hc/en-us/articles/12899607716493-Set-up-an-API-request-action
• Create an API request in your Zaps: https://help.zapier.com/hc/en-us/articles/12899473501453-Create-an-API-request-in-your-Zaps
• Supported apps for API Request actions: https://help.zapier.com/hc/en-us/articles/19055937195149-Supported-apps-for-API-Request-actions

Hopefully, this helps.

Hi Ken

Would you be able to provide an ETA on the resolution? I am assuming that Zapier is aware that not having this “objects visbility” is putting out any existing or future Salesforce NonProfit Cloud user that would like to use Zapier for any kind of integrations.

Meaning $$$ no new clients on Zapier, maybe that would change the priority on the API update for Zapier Salesforce integration…

Any feedback would be highly appreciated

@ken

If I am not able to see a NPC Object like Gift_Entry in the Salesforce instance, how would I be able to use the API Request (Beta)? if when I do the request or push the object is not found

Until the connection I am using is not upgraded it to be able to reach all the Objects this work around does not work either, am I right?

Waiting your feedback

Hi @FosterFamily,

Unfortunately, we are unable to provide a precise ETA for the implementation of these features. This is due to the fact that there are over 5,000+ different integrations on Zapier, and priorities are constantly changing. Additionally, there are many variables at play, some of which are beyond our control (such as being reliant on partners to make changes).

As a result, it is not possible to offer accurate timeframes for feature requests. With that said, we want to assure you that the feature has been logged and we are working on resolving it as quickly as possible.

We will notify you as soon as it is resolved. In the meantime, I am doing everything I can to pass on feedback like this to ensure that the impact of these issues is clearly understood.

Additionally, you can reach out to our Zapier Experts so that they can help you setup your API Request (Beta) or Webhooks setup. Again, those objects can be found as long as the Salesforce API supports it.

You can reach our Zapier Experts here: https://zapier.com/experts

Hopefully, this helps.

​@FosterFamily so the trick here is to not rely on any iPaaS or OOTB connector app to work with NPC. Since Nonprofit Cloud (NPC) is so new, most market-leading nonprofit tools haven’t caught up to its data model, relationships, and best practices.

My recommendation for any app you want to integrate with NPC: A "integration open" strategy using a staging/intermediary custom object in Salesforce is a smart and scalable way to manage this uncertainty.

Instead of letting Zapier push 1:1 API calls into NPC objects, you batch data into your staging object, and let Salesforce's scheduled Flows efficiently transform and map the data.

Made-up example:

1. Create custom Object "Stripe Payments" (Stripe_Payment__c) …. this is our “staging” object
2. Use Zapier/Workato to Push Data to the Staging Object
   1. Trigger: New payment event in Stripe.
   2. Action: Create a new Stripe_Payment__c record in Salesforce.
3. Create a Salesforce Schedule Triggered Flow to Process Data
   1. Runs every X minutes or hourly.
   2. Finds Stripe_Payment__c records in New or Queued for Processing status.
   3. Transforms data based on NPC rules.
   4. Creates:
      1. Opportunity + Payment (if treating as donations).
      2. Recurring Donation / Recurring Payment (if applicable).
      3. Updates Stripe_Payment__c.Processing_Status__c = "Processed".