Imagine if you’re a third-party developer creating integrations with the Salesforce Nonprofit Starter Pack (NPSP). Right now, you need to build services on your own that manage the routing of data, creates matching between inbound data and existing data in the NPSP, and much more. With the NPSP spread across multiple Salesforce packages, integrations for donations, event registrations, and more can be quite cumbersome.
What if instead, the NPSP had a pre-built set of APIs that you could tap into, providing you a landing zone for your inbound data. A location where you needed to know little-to-nothing about the NPSP, but your organizational clients could know that their data was being properly routed to its own home.
Well my friends, a few good folks from the NPSP developer sprint in DC this week have started to make this happen. Life as we know it for ISVs will become much better.
Currently, you can view the work of Kevin, Evan, and Nick in the GitHub repository. It’s an early start, and long way to go, but seeing their progress thus far has us at PICnet very happy. By having an API for the NPSP, we’ll be able to focus our energies on the gorgeous web front-ends our clients are looking for in Soapbox Engage, to do things like donation pages, online event calendars, membership sign-up forms, and more.
During the sprint, it was great to watch the conversation about this start with a payment processing service and move into a full-blown API service for the NPSP. The NPSP is in good hands with the architecture leadership of these folks, and we’re looking forward to seeing what gets accomplished in the upcoming months.
Nonprofit news, strategy, and tactics sent straight to your inbox
Sign up for the Soapbox Engage newsletter
This entry was posted on Thursday, December 6th, 2012 at 9:00 am and is filed under CRM, Integration, Salesforce.com, Soapbox Engage. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.