I want to create an efficient WF that looks at a text and based on that text saves a data type from my option set.
I could tell you a lot of different ways to make that entire process much more efficient in terms of speed to process and WU costs of running as well as improving speed and reducing WU costs of retrieval of that information, but without needing to change the setup you’ve already implemented, you can follow the below.
- Go to Plaid and find their entire list of categories with the exact formatting they provide it to you in (so if the categories are listed as “Bank Fees” on their site, it is possible that in your webhook it comes back as “bank_fees”)…it is essential to make sure you have the proper formatting and naming conventions that you will be receiving from the Plain webhook.
- Once you have that list, you will create your option set of Categories. Your display values must match exactly the values Plaid provides in the webhook, if not, it won’t work.
- Once you’ve add all the categories to your option set, go to your webhook and update the ‘detected data’. You do this by pressing the Modify Types button.
- Then when the screen opens to initialize the data, next to your category field you will from the dropdown change it from text to the option set you created previously.
- So, now whenever a webhook is received from Plain the response will return the value of category not as text but as your option set value that matches (again, make sure the display value, which is the ID, is formatted exactly as Plain sends it via webhook for matching to work).
- Now you can just save the value in one action, no recursive flow necessary or any get option filtering : first item necessary, and if there is a list of categories, it would work just fine as well.
Ohhh yep this make sense. I will do this! Thanks!