<?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/f738f4e8e06640d9ac79b7c56c83af4a&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/f738f4e8e06640d9ac79b7c56c83af4a-90a2c91405c3e62d.gif</thumbnail_url><duration>210.23</duration><title>Navigating CRM Integration Challenges and Solutions</title><description>In this video, I discuss the challenges I&apos;m facing with the new integration type in our CRM, particularly how it affects the event type field, which is currently a picklist. I realized that the new integration requires a different setup that conflicts with our existing communication processes, as I can&apos;t change over 60 pieces of communication that rely on the current fields. I&apos;m looking for guidance on how to proceed since I can&apos;t modify the API calls either. I would like to know if we can revert to the old CRM integration to avoid these complications. Any help or suggestions would be greatly appreciated.</description></oembed>