<?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/11914893d9e64d81834455abb450e69b&quot; frameborder=&quot;0&quot; width=&quot;1918&quot; height=&quot;1438&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1438</height><width>1918</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1438</thumbnail_height><thumbnail_width>1918</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/11914893d9e64d81834455abb450e69b-739da95da920b9ca.gif</thumbnail_url><duration>247.388</duration><title>Provider Notification for Multi Send Transactions</title><description>I shared a solution for the provider notification automation. First key point, you cannot get a different provider level transaction hash for payments inside a multi send, since all child payments share the same parent hash and the provider specific identifier is the log event. I changed the workflow to include the parent transaction hash, log index, provider transfer, and provider wallet URLs so providers can pinpoint their payment. For the demo, I deleted four records, ran the workflow, and sent notifications by Slack and email for Coinmetrics, DRPC, and two New Change of VEX. I then ran it again after fixing an Alchemy email so only one email came through with no error.</description></oembed>