Need some help building a WITHINGS workflow

Help me Build my Workflow
1

Hello.

I’m new to n8n. Maybe this workflow is too ambitious, i don’t know : i’m trying to set up a workflow around WITHINGS data, by using the WITHINGS connectores, and i’m not able to have anything working.

Could someone point me in the good direction ?

  • Which WITHINGS nodes should be installed ? This is incredibly confusing :
    • There are two different community nodes (see : Search n8n nodes | NCNodes)
    • There are different “oauth2” associated nodes (the “default” one and a “custom one”)
    • Even worse, depending “what is installed first”, it seems the final behavior is totally different ! (the fork of the WITHINGS node and nothing else (OAUTH2 retrieved as a dependency), or first the custom OAUTH2 then one node or the one, etc.) - then some fields / buttons are available … or not !
    • So what exactly should be installed, and how ?
  • How to configure the OAUTH2 part regarding withings ? This is not clear at all (related to previous question : depending what is installed and even HOW it is installed, the available fields are very different)
  • How to have a fully working / complete workflow ? Is there a recipe / example somewhere ?
    • Which connectors should be chained / in which order / with which operation ?
      • “Withings Dummy” ?
      • “Withings Token Exchange” ? (with which operation ? what to input in these fields ? etc.)
      • etc.
    • I have of course set up a Withings developer API on their website (and the associated “credentials” part in N8N seems ok)

It’s my very first try with n8n and i have to say i’m quite disappointed by how unfriendly this is (at least for beginners). I did many tests, installing, removing, restarting from scratch, trying to configure OAUTH2 for this node … nothing worked, even after hours of testing.

Any help would be appreciated.

image
image1340×240 16.3 KB

image
image1282×308 17.3 KB

image
image1375×364 28.4 KB

image
image1233×624 29.5 KB

2

welcome to the n8n community @SR-G
I’d simplify this first and avoid mixing community packages. Since Withings is coming from community nodes, I would install only one Withings package, remove the other fork or custom OAuth variant, restart n8n, and build a small test workflow with just the Withings credential and one read operation. If the credential test works but the Token Exchange node still asks for authorization code and redirect URI manually, I would not keep chaining Dummy and Token Exchange nodes as a beginner flow. At that point the safer workaround is to use the HTTP Request node with a standard OAuth2 credential configured from the Withings developer app, because n8n documents community nodes as third party packages and their behavior can differ depending on the package implementation.

3

Thanks for your answer.

Regarding the nodes to activate in the workflow (Dummy, Token Exchange, …)

I had of course tested several times with a more simple workflow than in the screenshot just before (like, only the “Get Data” step + a trigger). But it was failing. Hence at some point some tests with the other components provided by the withings community node (but without knowing what exactly should be used and in which order). Hence the question in the first post.

Regarding the OAUTH2 mechanizm.

So if i understand correctly, you are suggesting to use the “default OAUTH2” n8n node. But then i’m quite confused because the developers of the Withijngs n8n community nodes are expressively stating everythwere than the Withings auth is a non-standard one and that the default n8n OAUTH2 node will not work. Example :

image

image
image1221×213 32.8 KB

So … it’s confusing. Are you really sure that it will work with the default n8n OAUTH2 node ?