Impact on transfer of Xano workspace to other instance

Ask us anything
1

Hi there,

I have a working application in Weweb linked to Xano. We are using the Xano Auth plugin and Xano Datasource Plugin with several Xano Collections.

Due to several reasons we are now planning the transfer of the Xano workspace to a different Instance. In this instance we also will generate the new Metadata API Key.

Has anyone else performed a transfer like this. I want to get insight in the impact that this transfer will have within Weweb. Things that already come into my mind are:

  • Reinitiate/Reconfigure the Auth and Datasource plugins, because Metadata API Key, Instance and Workspace will change?
  • Reinitiate/Reconfigure each distinct Xano Collection, because endpoints will change?
  • Check workflows that are using direct Xano API Requests, because endpoints will change?

Questions:

  • Are the above assumptions correct? Or do we need take something else into account?

  • Is it expected that we also need to remap input variables used in Xano Collections and Xano API Requests (in workflows) after reconfiguration (which will imply quite a lot of effort) ?

Thanks in advance.

2

I have done this and your assumptions are correct and you will also need to remap the input variables when you update the endpoints (group and specific one). I found it less error prone to duplicate the workflow action (Xano request), set the endpoint, and then set the input variables. I would use the original to reference and/or copy the input formula. Then either deactivate the original or delete it. If you instead just update the endpoint on the original action, it clears the input fields.

It’s a major pain and I won’t make that mistake again!

1 Like