OS migration note for Cliniko and Nookal users
During the Motics OS migration, some Cliniko and Nookal integrations need to be reconnected with the clinic's API key. This is expected and does not mean your Motics account, sessions, notes, or EHR data have been deleted.
If Motics shows an authentication error, missing credentials, disabled integration, no patients recognised, or asks you to reconnect Cliniko or Nookal, go to Settings > Integrations, open the relevant integration, re-enter or verify the API key, save the connection, then retry the push.
If you are busy in clinic
Use Copy with preserved line breaks and paste the note manually into the EHR. This is the fastest temporary workaround if patients are waiting or you do not have the admin/API-key access to reconnect immediately.
Reconnect the integration later the same day when you have the API key or the clinic admin is available.
Common causes
Credentials - expired or missing API key, or integration disabled.
OS migration reconnection - Cliniko or Nookal needs the API key saved again.
Patient link - session not linked to the correct patient.
Nookal - wrong region or unmapped patient.
Meddbase - referrer contact missing an address or letter type not selected.
Quick recovery steps
If you are in clinic and need speed, copy/paste the note into the EHR first.
Open Settings > Integrations.
For Cliniko or Nookal, re-enter or verify the API key and save.
For Nookal, confirm the correct region.
Open the session and verify patient mapping and the latest summary version.
Retry the push.
Escalate to Motics support
Escalate if the API key has been re-entered and saved but the integration still fails, no patients are recognised after reconnecting, the integration is missing from Settings, or the user cannot get API-key access through their clinic admin.
Include organisation name, EHR provider, exact error message or screenshot, whether the API key was re-entered, whether no patients are recognised or one patient is missing, and Nookal region if applicable.