Opero Docs
Opero10. Integrations

Integrations with other systems

Opero potrafi wymieniać dane z innymi programami: sklepem, systemem księgowym, kalendarzem. Oznacza to dane, które pojawiają się same, i mniej przepisywania.

What a systems integration means

An integration is a connection between Opero and another program through which data passes between them without manual retyping. An order from a shop can create a matter in Opero by itself, and data from invoices can go to accounting without sending a spreadsheet by e-mail.

An integration is usually invisible to the user. It shows itself in something appearing by itself or in your not having to enter something a second time in another place.

How to tell that data came from outside

  • A record no one created by hand. A matter appears in the list because another system created it.
  • A "system" author in the history. At a change there is a mark of an automation or a connection, not a first and last name. This is intended behavior.
  • Fields no one filled in. The data came from outside together with the record.

Example. A client places an order in an online shop. In Opero a new matter appears with the client's data and the order items, even though no one on the team entered anything. You handle the delivery, not the retyping.

What to do with wrong data from an integration

Integrations can be sensitive to changes on the other side. If you see that something came in incomplete or strange:

  • Do not fix it yourself on every occurrence. If the same error returns on every record, the problem is in the connection, not in this one case.
  • Report it to the administrator with specifics: which record, when it appeared, what is wrong. The administrator will read from the system what exactly came from outside.
  • Do not create a record by hand "just in case", if you expect it to come from the integration. You will duplicate the matter.

Limitations of an integration

An integration moves data, but does not decide for you. What is to happen with a brought-in matter is still described by a process in Opero: who verifies it, who approves it, when it is closed. A connection with another system does not replace the established flow.

On this page