{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/11914893d9e64d81834455abb450e69b\" frameborder=\"0\" width=\"1918\" height=\"1438\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1438,"width":1918,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1438,"thumbnail_width":1918,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/11914893d9e64d81834455abb450e69b-739da95da920b9ca.gif","duration":247.388,"title":"Provider Notification for Multi Send Transactions","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."}