<?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/dc01ec8b55e94504bcafa8bcaa25107d&quot; frameborder=&quot;0&quot; width=&quot;3868&quot; height=&quot;2901&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2901</height><width>3868</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2901</thumbnail_height><thumbnail_width>3868</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/dc01ec8b55e94504bcafa8bcaa25107d-29409ac052b4b0ec.gif</thumbnail_url><duration>214.7</duration><title>Passing Context / Variables in Unmeshed Workflows 🌟</title><description>In this video, I explain how to effectively pass context between steps in your process definitions using Unmeshed. I cover the templating format, including how to use secrets and environment variables, and provide examples of syntax for referencing outputs from previous steps. It&apos;s crucial to understand these concepts to control the behavior of your definitions during execution. Please take a look at the detailed examples in our documentation for further clarity.</description></oembed>