Self-hosted
When I turn in 2FA in self-hosted baserow I get the following error in the n8n baserow node. Turning it off solves it.
{ “error”: “ERROR_INVALID_CREDENTIALS”, “detail”: “No active account found with the given credentials.” }
Maybe I’m doing something wrong, in that case node documentation need updating?
Hey @contentpeter, I’m afraid the current Baserow n8n node is not compatible with the 2FA in Baserow. This is because it uses the email+password authentication, and that one now requires a 2FA token.
We’ve made efforts to update the Baserow n8n node here: Baserow node update batch operations, additional filters, and token auth by bram2w · Pull Request #19758 · n8n-io/n8n · GitHub, but n8n would need to do a final review and merge the changes in their codebase. Once that it merged, it will be possible to provide a database token, which doesn’t need the 2FA step.
It would be great if you can respond to that pull request and ask them what the state is, explaining the situation with the 2FA. It might help to get it through faster.