<?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/62f94ce6959945c0b6671e312a4e6218&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/62f94ce6959945c0b6671e312a4e6218-f4a86f1b9b73cdea.gif</thumbnail_url><duration>295.922</duration><title>Using a script to clean up Variables in Postman: Tips and Tricks 💡</title><description>In this video, I’m responding to a challenge response from our community, about managing environment variables in Postman, a common issue I&apos;ve faced myself. I walk you through a customizable script I&apos;ve created and stored in our package library that allows you to clean up variables based on different scopes while preserving certain ones, like a baseUrl. I demonstrate how to implement this script in a request and show the logging feature that tracks what gets cleared or kept. If you find this helpful, I encourage you to modify the script and share your own implementations with the community.</description></oembed>