I’m trying to pair self-hosted NocoDB instance with self-hosted Activepieces but the integration seems to don’t work.
That happens when I try to select the Workspace ID (NocoDB):
I tried another blocks and they are OK:
Any help would be greatly appreciated 
Bump
I’m having the same issue!
Hello @BB_Visual @orwellwasright ,
Could you please run the following command and let me know the output you get for your NocoDB instance?
curl -X GET "https://YOUR_INSTANCE_URL/api/v1/workspaces" -H "xc-token: token" -H "Content-Type: application/json"
Make sure to replace YOUR_INSTANCE_URL with the actual URL of your instance.
My bad, thanks. I need to configure the /api/ access from my Nginx reverse proxy.
I’ll try to figure it out and/or ask on NocoDB community as well
No problem! Let us know if it doesn’t work after you configure the Nginx proxy.
Hello all, I am having the same issue. I was wanting to use internal IP instead of a hostname. I did setup a temp domain (host) name and get a Bad Request. I am using Nginx Proxy Manager as well. But, when I use my internal IP, i get no response as if curl did not run? I also, am able to connect to Db, if I manually input the ID’s for table, workspace, etc. using the generated token from NocoDB… Any thoughts on this? It does not auto list the workspaces, tables, etc…
Thank you for the guidance.
It’s something related to self-hosted instances, the plugin should differentiate the type of instance connected and choice the correct endpoint:
Got It. Thanks for updating. I will update the piece.
Nice, thanks!
There is an estimated ETA? I’m excited about using ActivePieces in our workflow
I would like to see this updated as well. It would be greatly appreciated!
Thank you
We are still waiting and I think there is a few changes to be done.
No rush but can we know if you really will update the plugin @kishanprmr or how to contribute?
I have opened the Ticket regarding the dropdown issue in self-hosted NocoDB instances.
Since self-hosted instances don’t have multiple workspaces, the dropdown will be removed.
Unfortunately I had to move to N8N until this gets really resolved.
Still looking for a solution or workaround. An opened issue on Github isn’t work on my instance.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
