<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/ec904344359643b7a02a250ad94ec96b&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ec904344359643b7a02a250ad94ec96b-5b7dbb48b4ef60e0.gif</thumbnail_url><duration>283.407</duration><title>Related Contacts Workflow, Pably and HighLevel</title><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.</description></oembed>