Follow customer details, work status and invoice data through three fictional systems. See why each integration field needs an agreed source and direction.
The spoken explanation, organised by chapter.
This accompanies our article on connecting software. When CRM, scheduling and accounting exchange information, define which application may change each field.
In a fictional organisation, a customer order moves from CRM to scheduling and then accounting. Meanwhile, someone changes an address. Which application should distribute that particular change?
The CRM owns customer details, scheduling owns execution status, and accounting owns invoice numbers. These fields travel in agreed directions without casually overwriting fields owned by other systems.
Specify source, destination, stable reference and transfer trigger for each field. Define clearing, archiving and deletion too. Two-way synchronisation is not blanket permission to update every available field.
An address change from CRM may reach scheduling. An execution status changed there can return as status information, without automatically changing the customer details held in the CRM.
A change arriving from the wrong source, or without a customer mapping, needs explicit handling. An apparently successful connection must not hide a failed or incorrect data transfer.
Compare records over the same period. Which changes arrived, which are missing and which await recovery? Show administrators the last successful processing time and the required freshness.
Choose one operational problem and test creation, changes, deletion and recovery after failure. Check whether an existing connector supports these agreements before developing a custom integration.
Good integrations preserve meaning and responsibility as they transfer information. Our source article on software integrations helps define sources, directions, exceptions and maintenance in practical terms.
1:52An illustrative CRM request shows how an API integration handles repeated messages, invalid fields and a timeout whose outcome has not yet been established.
Source articleAPI integration for connected business systems
1:58An illustrative CRM example explains stable source references. See why matching rules, shared email addresses and human review matter when linking customer records.
Source articleCRM integration with accounting and business systems
1:52Use a fictional service request to see how teams can automate handovers with clear information, meaningful states, accountable owners and exception paths.
Source articleBusiness process automation