Skip to content
Process Automation· Part 5 of 7

Connecting Your Systems: The End of Copy and Paste

Short answer

Connecting systems means each piece of information has one owning system and moves to your other programs without copy and paste. Part 5 of the process automation series explains the 3 elements of any integration, 3 ways to integrate and when each fits, and a copy and paste mapping exercise.

Origami Team

Editorial Team · · 7 min read

Share on WhatsApp
Like what we publish? Pin Origami as a preferred source on Google.Add as a preferred source on Google
Connecting Your Systems: The End of Copy and Paste

Connecting your systems means every piece of information has one system that owns it, and it moves from there to your other programs automatically instead of an employee copying and pasting it. In part 4 of the series you had the system read the document. This fifth part of 7 answers what comes next: where does the data go? You leave with 3 elements of any integration, 3 ways to integrate and when each fits, 4 questions to ask before any integration, and an exercise to map every copy and paste in your business. For the broader picture of system integration, see System Integration: How to End Data Silos; here we focus on the method step by step.

Where copy and paste happens today

Most businesses run several programs side by side: an accounting program, a sales system or online store, an Excel file for stock, and an HR system. Between every two programs stands an employee moving data by hand, in situations like these:

  • The customer order: it arrives from the store or a sales rep, then is keyed again into accounting and into the stock file.
  • New customer details: typed into the sales system, then typed again into accounting at the first invoice.
  • A stock transfer: an item moves from a warehouse to a branch, is recorded in a file, then the accountant is told about it in a message.
  • The weekly report: an employee assembles it from three programs into one file every week.

The employees who do this today are the ones who know where names and numbers differ between programs, so they are the first people to ask before any integration. The problem is not their accuracy; it is that one piece of information lives in more than one place, so when it changes in one it stays out of date in the other.

Three elements of any integration

Whatever the tool, every integration rests on 3 elements you can explain to your team:

  • One source for each piece of information: decide which system owns each item. Customer details might be owned by the sales system, balances by accounting, quantities by the stock system. Changes happen only in the owning system; the others read from it.
  • A carrier that moves the data: usually an application programming interface (API), an official door a program opens to send and receive data in an orderly way, or a ready connector built on top of that door. We explained the idea in detail in APIs: How to Connect Your Business Systems.
  • A trigger that starts the transfer: an event that sets it off, such as a new order or an approved invoice, or a fixed schedule every hour or every night.

If you do not settle the first element, the integration will not solve the problem; it will just move the conflict between programs faster.

What happens when the other side is down

This is the question many forget. The program you connect to may stop for maintenance, respond late, or reject an incomplete record. A good integration handles this in a way agreed in advance:

  • Retry: the integration keeps the record that did not arrive and sends it again later instead of losing it.
  • No duplicates: if the same order is sent twice, the receiving system knows it is the same order and does not record it twice.
  • An exceptions list: a record rejected for a clear reason, such as a customer with no number or an unknown item, goes to a list a named person sees and corrects.
  • An alert: if the whole integration stops, its owner is alerted at once, not after the accountant discovers at month end that the figures do not match.

3 ways to integrate and when each fits

  • A ready connector: many programs come with built-in connections to common programs, such as an online store with an accounting program. It fits when the connector covers what you actually need without changes, and you lose flexibility when your way of working differs from what it was designed for.
  • No-code automation tools: tools that link many programs through steps you build yourself. They fit simple, limited integrations; we compared them with a custom build in No-Code Automation vs a Custom Build.
  • A custom integration: built around how you work, it fits when rules and exceptions pile up or when the other program is an internal system with no connector. You will find examples linking sales, stock and accounting in Workflow Automation Across CRM, ERP, and Accounting.

Before any of them, ask 4 questions: which system owns this information? What triggers the transfer? What happens when the other side is down? And where does the data pass through? The last one matters when the data carries personal information. The Personal Data Protection Law published on the SDAIA site requires the controller in Article 19 to take the organizational, administrative and technical measures that protect personal data, including when it is transferred, and Article 29 sets conditions for transferring personal data outside the Kingdom, which concerns you if your integration tool runs on servers abroad. Confirm the details with SDAIA or a lawyer; this is not legal advice.

The Origami view

We are a Saudi technology company that builds systems, apps, integrations and AI solutions. When we build an integration, we start with a simple table drawn up with the employees who move the data today: each piece of information, the system that owns it, and the programs that need it, because that table settles half the decisions before a single line of code.

We design the failure path before the success path: retries, duplicate protection, the exceptions list, alerts, and a named owner for every integration. An integration that works on a normal day is easy; the one you can trust is the one whose behaviour you know on a bad day. You will find the details of what we build on our services page.

Exercise: the copy and paste map

Over one working week, ask each department to record every time it moves data from one program to another, in a table of 5 columns:

  • What information was moved: a customer, an order, a quantity, an appointment.
  • From which program to which, including WhatsApp and Excel files.
  • How often it happened in the week, and how many minutes each time takes.
  • Which system should own this information in the team's view.
  • Whether it carries personal data, such as a customer name or mobile number.

Sort the rows by time spent, and start with the integration that recurs most and where departments agree on the owning system. That figure, measured by you, is more honest than any general savings percentage.

In the next part

Once automations and integrations start acting in your company's name, they need controls. Part 6 of the series, Automation Controls: Logs, Permissions and Data Protection, explains run logs, permissions to change a workflow, an owner for every automation, and what the Personal Data Protection Law requires.

Sources

  • #Make the Most of Tech
  • #Process Automation: From Manual Task to Running Workflow
  • #Process Automation
  • #Workflow

Frequently asked questions

What does connecting business systems mean?

Each piece of information, such as customer details or quantities, has one system that owns it, and it moves from there to your other programs automatically through an API or a connector, instead of an employee copying and pasting it.

What is the difference between a ready connector, no-code tools and a custom integration?

A ready connector comes with the program and fits when it covers your need as is, no-code tools fit simple and limited integrations, and a custom integration fits when rules and exceptions pile up or there is no connector for the other system.

What happens if one of the connected programs goes down?

A good integration keeps the record and resends it later, prevents it being recorded twice, sends rejected records to an exceptions list a named person reviews, and alerts the integration owner as soon as it stops.

Does it matter where the integration tool runs?

Yes, if the data is personal. The Personal Data Protection Law requires protective measures in Article 19, including during transfer, and sets conditions in Article 29 for transfers outside the Kingdom, so confirm with SDAIA or a lawyer.

Have a project in mind?

We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.

See our services

Newsletter

New articles and series, in your inbox.

Follow Origami in Google

Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Add as a preferred source on Google