Before reconnecting anything, check which workspace you are in. Many missing connections are simply in another workspace or hidden from the current role.
Check the basics
- Confirm the workspace name and clear any list filters.
- Refresh the page once and inspect the connection status.
- Ask the owner to check your access if the connection is visible to them but not to you.
- Read any error shown during authorization and keep its wording.
- 1Filter integrations by Commerce.
- 2Open the store integration you need.
Salla: pairing is still pending
Generate a fresh code from the intended Botat workspace if the previous one expired. Paste it into the Botat connection-code field in Salla’s app settings and save the form. Check that you installed the app in the same store you are trying to link.
If the store is linked but authorization is still pending, wait for the installation authorization to complete and check the connection again. If another workspace already owns the store, contact support to review the ownership instead of creating repeated connections.
WhatsApp or Zid: authorization did not finish
Allow the authorization window, use the correct merchant or business account, and complete all steps before returning to Botat. If a connection already exists, use its reconnect action when available.
Rekaz or website chat
For Rekaz, check the tenant and the registered webhook address as separate setup items. For website chat, try the share link: if it works, investigate the website embed; if it does not, investigate the inbox first.
Still unresolved
Collect the workspace, connection type, approximate time, and exact error. Use the support checklist. Deleting a connection can affect workflows that use it, so do not use deletion as the first troubleshooting step.