<?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/6beacdeced204c02a9243a251a7d2302&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/6beacdeced204c02a9243a251a7d2302-f44ff939f6fe51d7.gif</thumbnail_url><duration>123.141</duration><title>How Webhooks Push Data Into Third Parties</title><description>This Loom explains how to enable and use webhooks to send automated updates from your system to third-party software. It describes pushing information when quotes are approved, canceled, drafted, or rejected or sent, including customer name, quote value, and date. The Loom also covers job events such as assignment, completion, and cancellation, including final invoice value, to support reporting needs like Google Ads performance. For example, when a $5,000 job is completed after a call from an ad lead, the data can be sent back to a marketing agency’s reporting tool.</description></oembed>