--- title: Scenario blueprints slug: blueprints description: Export and import scenario blueprints to back up, reuse, and share your automations image: https://archbee-image-uploads.s3.amazonaws.com/oAyFj2GHlBeBVWF5OAir2/UgT6ALkSSWzuiIQg5i822_4.png docTags: createdAt: 2025-05-21T11:03:37.945Z --- In Make, you can save or copy scenarios as **Blueprints** and share them with other Make users within or outside your organization, or use and reuse them for your needs. A blueprint is a reusable version of a scenario that includes: - Scenario modules - Module settings - Mapped values Blueprints help to set up automations quickly, without having to start from scratch. You can: - Back up your scenarios in case you lose access to or switch to another Make account. - Export and save a blueprint to reuse a scenario later. - Share a blueprint with other users, who can then import the file or paste the JSON and run the scenario as-is or adapt it to their specific needs. - Copy a blueprint and paste it into other scenarios in Make, LLMs, or other relevant platforms. :::hint{type="warning"} While blueprints include scenario modules, settings, and mapped values, users still need to [create connections](https://help.make.com/connect-an-application#QzWef) for their accounts after importing the blueprint. ::: ::embed[]{url="https://www.youtube.com/watch?v=bt9EydXoHK4"} ## Export a blueprint You can export a blueprint of the scenario as a `.json` file. To export a blueprint: ::::::WorkflowBlock :::WorkflowBlockItem Click Scenarios in the left sidebar. Choose an existing scenario, or click **+ Create a new scenario**, if you need to create the scenario first. ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/d6pT0Xe-ljGjZ9nXiyx6I-20251001-152632.png) ::: :::::WorkflowBlockItem If it's a new scenario, add modules and [configure the module settings](https://help.make.com/module-settings). If it's an existing scenario, check that all of them are set up correctly. ::::VerticalSplit{layout="middle"} :::VerticalSplitItem ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/_GISVgX7C5_VfSraVGi7F-20251001-152717.png) ::: :::VerticalSplitItem ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/DUb4kvqu6f__ZEwyj-G1E-20251001-152747.png) ::: :::: ::::: :::WorkflowBlockItem In the upper right corner of the Scenario Builder, click the **three dots** **>** **Export blueprint**. ::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/IS7LhhQ1Ka8NmOxWiiKpG-20251104-114924.png" size="60" width="1558" height="1014" position="center" darkWidth="1558" darkHeight="1014" showCaption="false"} ::: :::::: Once exported, the blueprint downloads to your device as a `.json` file. ::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/5qi2Ue5_Ah6ilGn3ggk2n-20251015-102626.png" size="50" width="1079" height="792" position="center" darkWidth="1079" darkHeight="792" showCaption="false"} The file is typically named after your scenario. For example: - If your scenario's name is "New prospect notification", the file will be called `New prospect notifcation.blueprint.json`. - If the scenario has a default "New scenario" name, Make names the file after the modules in the scenario, e.g.,`Integration Google Forms, Google Sheets.blueprint.json`. ::Image[]{src="https://app.archbee.com/api/optimize/PL8X94efBsjvhfQV3wyyj-qzh9fMSCOPod8wSEybfwD-20250630-134806.png" size="26" width="626" height="376" position="center" darkWidth="626" darkHeight="376" showCaption="false"} You can now share this file with other Make users or keep it for your own future use. ## Import a blueprint :::hint{type="info"} We recommend creating a new scenario before importing a blueprint. If you import a blueprint while editing another scenario that hasn't been saved, all the changes in that scenario will be lost. ::: You can import a blueprint of the scenario saved in `.json` format. To import a blueprint: ::::WorkflowBlock :::WorkflowBlockItem In the upper-right corner of the Scenario Builder, click the **three dots** **>** **Import blueprint**. ![]() ::: :::WorkflowBlockItem Click **Choose File, **select the blueprint file in .json format, and click **Save**. ![]() ::: :::: The imported scenario will appear in the Scenario Builder. You can now configure your own account connections, make any necessary edits to the scenario, schedule it, and click the **Save** icon. :::hint{type="warning"} The imported blueprint must be below 2 MB in size. If the blueprint exceeds the scenario size limit, you'll be unable to save the scenario and will see an error message. ::: ## Copy a blueprint to a clipboard You can also copy a scenario blueprint to the clipboard. The blueprint is copied as JSON text, which can be pasted into other scenarios in Make, LLMs, or other compatible tools. To copy the blueprint to the clipboard, click the **three dots** **>** **Copy blueprint to clipboard **in the upper-right corner of the Scenario Builder. ![]() To paste the blueprint into another scenario in Make: ::::WorkflowBlock :::WorkflowBlockItem Create a new scenario or open an existing one. ::: :::WorkflowBlockItem Right-click anywhere on the scenario canvas. ::: :::WorkflowBlockItem Click **Paste**. ![]() ::: :::: A scenario from the blueprint will appear in the Scenario Builder. You can now configure it, make any necessary edits to the scenario, schedule it, and click the **Save** icon. :::hint{type="info"} Check out the [Make Academy Blueprints course](https://academy.make.com/courses/take/BasicsC01/multimedia/41089201-unit-1-blueprints) to walk through a use case and see how blueprints work in action. :::