GoFundMe Pro's Salesforce sync went dark: a connected app checklist before November 30
Last week, a lot of nonprofits found out the hard way how much they depend on one quiet piece of plumbing: the connection between their donation platform and Salesforce. During a wave of coordinated bot attacks on fundraising platforms, the GoFundMe Pro integration with Salesforce was temporarily disabled as a precaution. Donations kept coming in. They just stopped showing up in the CRM.
At the same time, Salesforce has a hard security deadline coming up on November 30, 2026 that can break certain integrations without warning. If you run a small business or nonprofit on Salesforce, this is a good week to look at what is connected to your org.
What happened with GoFundMe Pro and DonorPerfect
According to The NonProfit Times, several fundraising platforms were hit in what looked like a coordinated, multi-pronged attack by AI bots. Here are the key points from the November 12 report:
- DonorPerfect's application went offline. Its parent company, SofterWare, said the attack began through its marketing website and has been contained. An official said an AI agent was "rapidly adapting its approaches and discovering new methods" to attack its systems.
- GoFundMe Pro stayed up, but its Salesforce connection was switched off. GoFundMe said organizations "can continue to safely receive donations."
- The practical result: some nonprofits could still accept online gifts but could not sync them to their CRM.
GoFundMe Pro's status updates later said the company had "addressed the known methods of unauthorized access" and believed the incident was contained.
This is not the first time this has happened. In August 2025, attackers took OAuth tokens and API keys from Salesloft's Drift integration, and Salesforce disabled all Drift integrations with its platform as a precaution. The pattern is now familiar: when a connected tool looks compromised, the connection gets cut, and every business relying on it loses its data flow until it is restored.
Why connected apps are the weak spot
Most small business Salesforce orgs have more integrations than anyone remembers installing: a form tool, an email platform, a payment processor, a scheduling app, maybe a script a former contractor wrote. Each one holds a key to your data. You do not control how well each vendor protects that key.
You cannot prevent a vendor from being attacked. What you can do is know exactly what is connected, remove what you do not need, and have a plan for when one of them goes dark.
The November 30 deadline: OAuth Device Flow
Separately from last week's attacks, Salesforce is tightening one specific login method. Starting November 30, 2026, Salesforce restricts the OAuth 2.0 device flow to local external client apps with a localhost callback URL, and there is no opt-out for apps that do not comply. Every connected app with the device flow enabled is considered non-compliant.
The device flow is the "go to this web page and enter this code" style of login. It is typically used by tools that do not have a browser, such as headless scripts, kiosks, and IoT devices. When enforcement starts, those clients simply fail to log in. Usually the first people to notice are the ones using the device or the report that stopped updating.
A 30-minute connected app checklist
You do not need to be technical to start this. You (or your admin) can work through it in one sitting:
- List every connected app. In Setup, open Connected Apps OAuth Usage to see what is actually authorizing into your org. Write down who owns each one and what it does.
- Remove what you do not use. Old trials, retired tools, and apps from former vendors should be uninstalled and their access revoked. Every unused connection is risk with no benefit.
- Check for device flow logins before November 30. Salesforce recommends reviewing Login History for entries with the login subtype "OAuth Device", which covers up to six months. Anything that shows up needs to be migrated or replaced.
- Ask your vendors. For apps you did not build, including managed packages, Salesforce advises contacting the developer for an updated version before enforcement.
- Plan for the "sync gap." If a key integration is paused for days, how will you catch up? Know where the source data lives (your donation platform, payment processor, or form tool) and how to backfill it into Salesforce once the connection returns.
- Rotate credentials after a vendor incident. When a connected vendor reports a breach, follow their guidance to revoke and reconnect. In the Drift case, Salesloft recommended that customers revoke and rotate their API keys.
What this means for nonprofits in particular
For nonprofits, the CRM is where donor acknowledgments, receipts, and year-end reporting come from. A multi-day sync gap in mid-November, right before Giving Tuesday and year-end appeals, is a real operational problem. If you use GoFundMe Pro, DonorPerfect, or a similar platform, confirm your integration is fully restored and that no gifts from the outage window are missing from Salesforce.
The bottom line
Integrations are what make Salesforce useful for a small team, and they are also where most of the risk sits. A short, regular review of what is connected, who owns it, and what happens if it stops is one of the cheapest forms of insurance a small business or nonprofit can buy.
Not sure what is connected to your org, or whether anything will break on November 30? Book a free audit and we will walk through your connected apps with you.
Sources
- The NonProfit Times: Breaking: Multiple Fundraising Platforms Targeted By Bots
- GoFundMe Pro incident history (status updates)
- Wikipedia: Salesloft (Drift breach, 2025)
- Salesforce Help: Security Change: OAuth 2.0 Device Flow Restrictions by November 30, 2026
- Software Insights: Salesforce Restricts the OAuth Device Flow on 30 November 2026