Adopt and edit existing KORONA calls

Use existing external system calls when your POS buttons or callbacks already point to them. Adoption keeps their KORONA IDs, numbers and references. You can manage several existing calls independently, even when they perform the same action.

Refresh and adopt

1. Open Admin > Integrations and find Existing external system calls below Managed callbacks.
2. Select Refresh from KORONA. This reads KORONA without changing its configuration.
3. Review the call's number, name, destination domain and GET/POST mode. A matching name alone does not identify the correct call.
4. Select Adopt for each call you want to manage. Adoption copies the reviewed settings into KORONA Event without changing KORONA or attaching new POS buttons. The call's status changes from Not adopted to Synchronized.

Calls on unrecognized domains aren't listed automatically. To add one, open Find a call by its KORONA ID, enter its exact KORONA call ID from KORONA and select Find call. The call is highlighted in the list; confirm it is the intended call before adopting it. Existing URL paths and credentials are hidden because they can contain secrets.

Choose a replacement for an action

When several adopted calls serve the same purpose, or a call is missing or belongs to a previous KORONA account, choose which existing call KORONA Event should use.

1. Refresh and adopt the intended call in the currently connected KORONA account. If it has a draft, conflict or failure, review Preview changes and complete Apply and verify first.
2. On that call, select Choose action.
3. Choose the KORONA Event action: a managed callback or a named saved view and its destination. Select Use for this action.
4. Selected for the next action confirms the choice was saved locally. KORONA has not changed yet. For a callback, use Synchronize and repair under Managed callbacks. For a saved view, retry publishing or removing it from its list.

Only existing actions are listed. If the saved view has not been published before, start publishing it from its list first. Choosing a call does not change its destination or other custom settings; review those settings before using it for an action.

If delivery-note processing is disabled, repair removes the selected callback from the current account's POS profiles and deactivates it. It does not enable processing or modify profiles in the previous account. A failed repair keeps the selected replacement available for retry. To choose a different replacement, repeat Choose action on that call.

Edit, preview and apply

1. Select Edit on the adopted call.
2. Change its name, number, display URL, callback URL, timeouts, request mode or activation setting. Leave a URL field blank to preserve the existing value. Existing credentials remain unchanged.
3. Select Save draft. The button is available once you change a setting. The call's status changes to Draft: a saved draft does not change KORONA and is not applied by background synchronization.
4. Select Preview changes and compare each setting's current KORONA value with its value after applying. Sensitive values appear as Hidden.
5. Select Apply and verify. KORONA Event checks the call again before writing and reads it back afterward. Last verified shows when the configuration was verified.

Approved custom settings remain the desired configuration during later synchronization. Updating account defaults does not replace those settings.

Resolve a conflict or retry

If the call changes in KORONA after preview, applying stops with the status Conflict. Select Preview changes again to compare the current KORONA configuration with your draft. Applying the new preview explicitly approves the displayed differences.

A failed operation affects that call's result. Review its error before retrying. If a request timed out, select Preview changes again: the change may already have reached KORONA, in which case verification needs no further write.

Writes stop when KORONA does not return usable credentials. Ask support to check the integration's access to the call before retrying. Hidden or missing credentials are never replaced with empty values.

A missing call is not recreated automatically. Restore it in KORONA or adopt another existing call and use Choose action to select it as the replacement. Switching KORONA accounts requires a fresh inventory and explicit adoption in the new account; old identities do not carry over.

See KORONA.studio synchronization for connection settings and ownership of shared data.