Orbit Node is not working

Questions
1

I am using the Orbit node (Resource: Member, Operation: Get, Workspace and Member ID are set) and trying to get member information. I get a 404 response code and cannot figure out why.

{"message":"404 - {\"error\":\"Not found\"}","name":"Error","stack":"Error: Request failed with status code 404\n    at createError (/home/n8n/.nvm/versions/node/v14.18.3/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/n8n/.nvm/versions/node/v14.18.3/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/n8n/.nvm/versions/node/v14.18.3/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (events.js:412:35)\n    at endReadableNT (internal/streams/readable.js:1334:12)\n    at processTicksAndRejections (internal/process/task_queues.js:82:21)"}

Because I thought, I might have set the wrong Member ID, I just used Operation: Get All. It still gives a 404 response. Also, turning off or on the Resolve Identities doesn’t change anything.

Using the HTTP Request node and the same API credentials and the same GET call, I do get a response.

Can somebody help me, investigating?

2

Hi @wohfab, many thanks for reporting this! From testing this on my own end I can confirm the behaviour. It seems n8n is using a workspace ID for its API requests instead of the workspace slug which is expected by the Orbit API.

I have prepared a fix for this:

Unfortunately, PRs tend to take a while before they are reviewed and merged. Until this is fixed properly, you could simply replace the dropdown value with an expression containing the slug of your workspace:
image

n8n will complain about this with the warning icon but you can ignore that, the request will work.
image

Hope this helps!

2 Likes
3

Hey @MutedJam,

wow, you’re very fast! This definitely helps for now. Thank you so much! :pray:
Will it break this work around, when the PR is merged? Just for me to keep track of it and not that I start wondering, why the workflow doesn’t work anymore when updating next time :wink:

1 Like
4

I don’t think you’d need to keep track of this. Once the fix is merged, n8n would internally use and store the workspace slug you’re already setting through an expression here. So the only thing changing once the fix is live would be n8n no longer showing you the warning icon next to the Workspace field.

1 Like
5

Perfect, thank you very much! Thread can be closed :slight_smile: Have a great and productive week!

1 Like
6

Got released with [email protected]

1 Like