I think I’m beginning to get it - the endpoint doesn’t need to be ‘triggered’ within the app - it triggers on its own as soon as the webhook receives the info. By that logic, as soon as info is sent to webhook, the below endpoint should save the data into the Plaid_Webhook table:
The thing is, it doesn’t… So, I’m either doing something wrong (most likely), Plaid doesn’t send webhooks for a sandbox version or I’m using the wrong webhook.
Tbe domain portion of the url will be the same as if you preview a page in a browser (like index). If you have not attached your own domain, it will be yourapp.bubbleapps.io. If you have attached your own domain, then use that. And yes, the whole thing breaks if that is not correct.
I don’t seem to be getting webhooks even after I updated the url. What’s the best way to troubleshoot this? Is there a way to see what webhooks were sent to that url?
I used the “Retrieve Item” API call and I can see that the webhook has been properly updated for that item. I also checked the url and the root of it leads me to the website (which lets me do believe the url is correct), but I can’t see how I can troubleshoot further.
Hi, I have tried using the Plaid plugin as well as the API plugin to get the user’s bank account details. However, after I sign in to my bank and select my account (Lets say I only select checking.) I am receiving both my checking and savings accounts even though I only selected one account. Is this normal behavior? How can I limit the API call to only return the 1 account?
Hey @adepew. The Get bank account details action uses this api call with plaid: API - Overview | Plaid Docs, which through the plugin gets all accounts for the item provided. So that is working as designed. You have a couple options:
Keep track of the desired accounts within your bubble db, and filter out what you don’t want to process. In my case, I store the plaid item in a thing, and then store the plaid accounts in another thing. Then I put the accounts in a list on the plaid item. The accounts have a simple yes/no flag to delineate which accounts are used within the app. When I get webhooks or the user initiates activity, I only process the accounts with include set to “yes”. I take this approach so that users can add other accounts later without having to reconnect with plaid.
An alternative is to create an API call that uses the same plaid api call linked above, but adds the option to retrieve only one account. I do this on a transactions call, but the same format will apply here on your /auth/get.
What is shown above is the call inside of a plugin, which is how I now handle all my auxiliary calls so that the client id and secret are not sent to the client, but allow me to have different dev and live values. But you can do the same thing within the api connector.