> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/bidirectional-data-flow.md).

# Bidirectional Data Flow

Visualization & Data Touchpoints

<figure><img src="https://2690571127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamdaMzHPLiZAT8YSfcpn%2Fuploads%2FEgxrpT52AEVWnhjtJ1UV%2FBildschirmfoto%202026-03-17%20um%2015.52.02.png?alt=media&amp;token=0736c899-c823-4715-a23e-758a46b56c4c" alt=""><figcaption></figcaption></figure>

### **Data Input**

New or updated data such as online donations, recurring donation updates, donation reversals, or payment gateway payouts across all FundraisingBox channels automatically triggers a webhook to the FundraisingBox NPC Connector.

To avoid duplicates, a two-step duplicate check is integrated. Learn more about our [duplicate management.](/knowledge-base/duplicate-management.md)

### **Donation Data Processing**

The Connector processes incoming data and updates the corresponding Salesforce NPC objects in real time.&#x20;

To enable seamless synchronization, the Connector maintains internal mappings and manages relationships and processing sequences between FundraisingBox and Salesforce objects. This ensures consistent, reliable, and accurate creation and updates of records across both systems.

### **Bidirectionality**

For inbound data from Salesforce, the Connector leverages filtered Streaming API PushTopics to capture only relevant changes.&#x20;

Manual updates made in Salesforce are automatically synchronized back to FundraisingBox, helping maintain data integrity and minimizing duplicate records.&#x20;

This bidirectional synchronization ensures that downstream processes such as account adjustments, updates for recurring payment or even triggering automatic direct debit collection run smoothly and reliably.

### **Error Logs**

In cases where data cannot be processed, error logs are generated to provide detailed information for efficient issue resolution. Depending on the nature of the issue, these logs are available either in the FundraisingBox Error Log within Salesforce or in the FundraisingBox Log Viewer.&#x20;

[Learn more about our error logs.](/knowledge-base/error-log-and-log-viewer.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/bidirectional-data-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.