{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/ec904344359643b7a02a250ad94ec96b\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/ec904344359643b7a02a250ad94ec96b-5b7dbb48b4ef60e0.gif","duration":283.407,"title":"Related Contacts Workflow, Pably and HighLevel","description":"I spoke with Ken about the Related Contacts workflow and concluded that what I have been trying to build is probably too difficult to do easily in Pably, so NA10 may be the better option. Instead, I set up a deviation where I return a JSON payload from the current Pably workflow, pass it into a custom field in HighLevel, and trigger a HighLevel workflow when that field changes. The idea is to run a code step to extract relationship IDs, make Clio API calls via webhooks, and write the resulting string of email addresses back into the related contacts field. I asked whether this approach makes sense versus rebuilding fully in NA10, and I requested Ken help to get the code step working together if we agree on the strategy."}