Make each connection serve a useful purpose
An integration should answer a practical question: what information needs to move, where should it go, and what should happen when it arrives? We start there when discussing connections for CentralBlock.
What needs to move?
Customers, jobs, invoices, bills, calls, photos. Name the records, not the system.
Where should it go?
Which system is authoritative for that record, and which one only needs to read it.
What happens when it arrives?
A record is created, a person is notified, a comparison is flagged for review.
Four kinds of connection, each with a defined scope
Our development direction includes connecting customer and job context with financial information, business communication, and marketing workflows. Each connection needs a defined scope and validation before it is used operationally.
Tell us which systems you use today and which records matter. Importing records, reading data, synchronizing updates, and writing changes back are different capabilities. Availability should be confirmed for the exact workflow you need.
The initial integration direction is read-only import and comparison of financial records. This does not imply two-way synchronization or replacement of your current accounting setup. Ask about current availability and validation for your records.
Connections to financial data sources depend on provider configuration and validation. Confirm the specific account or source, the data available, and the expected update behavior before relying on a connection.
Number routing, messaging, publishing, and channel reporting depend on the relevant provider and released product features. Tell us the service you use so we can discuss the specific requirement.
“Integrates with” can mean four different things
When you ask about a connection, ask which of these it is. They carry different risks and need different validation.
| Capability | What it means | Validate |
|---|---|---|
| Import | A one-time or repeated copy of records into CentralBlock | Field mapping, duplicates, what was skipped |
| Read | Ongoing read-only access for comparison and review | Freshness, scope, and where the source stays authoritative |
| Sync | Updates flow in one or both directions automatically | Conflict rules, ownership of each field, history |
| Write-back | CentralBlock changes records in the other system | Review step, permissions, reversibility |
Request a connection
Share the system name, the information you need to move, how often it changes, and which system should be authoritative.