In this video I show you a simple “hack” for Make.com: build reusable, modular scenarios by splitting recurring tasks into sub-scenarios and calling them like a toolbox. The goal is reusability: instead of copying huge scenarios again and again, I keep the logic in one place and just pass clean input parameters. That’s the difference between a one-off automation and a maintainable workflow library you can actually scale. I walk through a concrete example: a social posting workflow for LinkedIn, Instagram and X that I can set up in roughly 15 minutes and then reuse across multiple campaigns. We define a clear scenario structure, agree on input parameters, and centralize things like roles, tone of voice and prompts via a prompt registry. I also show how I integrate Flux image generation and—more importantly—how I keep it flexible by managing Flux versions so changes don’t break everything. The big takeaway: when something changes (new channel, new prompt, new image model/version, new account), you barely touch your main scenarios. You update the sub-scenario once, share tools via share links where it makes sense, and keep accounts/API keys/parameters configurable. That’s how I reduce maintenance, avoid duplication, and keep automations clean and debuggable.