Hello community, I have looked at these posts and I am still confused:
I need the general 1,2,3,4 steps. What to do First, second, Third, etc.
So I am setting up PLAID - Remember I am new to WAPPLER and this community. I am still trying to figure out all the various ways of setting it up on a no-code basis.
I am trying to follow directions and next is to Configure the Plaid Client in the Project. (I have already installed PLAID packages via NPM). I am confused as to importing the components as ai tried in the terminal 'IMPORT....' and nothing.
And if CSP directives need to be setup as well and how. (see screenshots)
As you can see in my screenshots below I have my Environment Variables setup, they do not show up when I try to link these variables to the PLAID 0Auth Security.
Next regarding setup up the APi itself, I am looking for a confirmation on how to set this up properly (YES I know to follow PLAID Docs, I am!). What type of table needs to be built and where to insert the correct PLAID credentials.
I understand how to call server connects, I will do this once I have this initial setup complete. The idea is to call this PLAID action for an on-mouse click during registration process. (I understand this already, just nothing before).
Yikes! That may as well been in Ukrainian for all I understood!
But seriously, I went to their website. Seems to be a North American service (Unless that is all it is showing me because I am in Canada)? If so, that may also be a reason for the lack of responses. This is a very specific API and I believe the Wappler user base from North America is comparably quite low in the big picture of things. At least on the forums. So getting an answer from someone that understands the issue may take some time.
Sounds like quite a complex and interesting project you have going. Good luck!
@franse I believe I am closer than I was thanks to that read. Here is where I am at.... I have successfully import and added all the components needed for PLAID. And now I am at the part where I exchange the USERID for the Secret Token from PLAID Api.
I have sent a test over to Postman (http://localhost:3000/api/create_link_token) with json body being { "userId": "{{identity}}" } - this works successfully in Postman and I get a token from PLAID, YAY!
But now the 'Not-so-yay' - I am getting a 404 error when I locally try to go to this URL (http://localhost:3000/api/create_link_token) which tells me something is not setup on Wappler side. Here is my API Action Properties screenshot. Do you see something wrong?
Just to confirm, I don't need to be creating a "New Server Connect Route"?
Because I already tested that as well and when I go to the localhost link I have a " {"status":"500","message":"A server error occurred, to see the error enable the DEBUG flag."} "
Btw what's on localhost:3000/api/create_link_token?
On the API url you're calling that..
It's not something like https://sandbox.plaid.com/link/token/create?
Asking this without any knowledge about how this api works
@franse So for Plaid, they want you to install various components on the server side where the Tokens and such can be Created and Exchanged on the backend is my understanding? So I create various components and installed their packages under the '/LIB' and '/webhooks' folders. With this it should be already configured to create this for you server-side.
You were not supposed to touch the lib folder, you'd be looking at creating a custom extension (check Wappler docs on the forum, there's a section for that) or using RunJS to call the Plaid client functions (you installed with npm)
Any changes you made inside lib folder may be lost upon a Wappler update.
You're using a relative URL, the Wappler editor doesn't know how to interpret that, you need to input the full (absolute) URL.
@Apple Your service has helped me very much. Wappler in-fact does not understand just '/api/...', it needs to be the full URL. My 'Fetch' Capability brings everything in now!
It's these fun little road blocks that get you into holes and sometimes you don't know how deep you are haha. One step closer, I am sure something will come up shortly here. So stay tuned.
So I have tested locally, to be able to send the USER ID as the {{IDENTITY}} and I receive back a Token. This is great. Only thing I am having trouble with now is sending the actual logged in user's 'user_id' instead of a blank input which comes back with an error. I know I am close just missing where to actually pull in the correct variable to use for this API Action.
I am sure i don't see something that someone else may. As you can see below, I have registered and I get the {{IDENTITY}} (user_id), but then when the next API Action is called (Create_Link_Token) then it says the user_id is missing and fails which means I am not telling WAPPLER the correct spot to grab this user's ID:
Thanks for that @Apple I tried updating that, unfortunately no luck. When I update the json body to your example, the 'Fetch' does not work and I get an error message. But having the json body like as: { "userId": "{{identity}}" } does work for the 'Fetch' to receive the Token.
Still need help forwarding the Identity over to the APi, this is a Wappler thing. Just not sure where to set up exactly to forward the userID after sign up....
I have tried many different options to try to set the 'client_user_id'
You need a way to see what request Wappler is sending, you can never work blind
Use a service like Mockbin or Beeceptor
After you set that up and see the issue, which I'm guessing is in creating the JSON object, you can try using the Group step to build the object and Set Values inside
