Scenario blueprints

in {{product name}} , you can save or copy {{scenario plural lowercase}} as blueprints and share them with other {{product name}} users within or outside your organization, or use and reuse them for your needs a blueprint is a reusable version of a {{scenario singular lowercase}} that includes {{scenario singular}} 's modules module settings mapped values blueprints help to set up automations quickly, without having to start from scratch you can back up your {{scenario plural lowercase}} in case you lose access to or switch to another {{product name}} account export and save a blueprint to reuse a {{scenario singular lowercase}} later share a blueprint with other users, who can then import the file or paste the json and run the {{scenario singular lowercase}} 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 while blueprints include {{scenario singular lowercase}} 's modules, settings, and mapped values, users still need to https //help make com/connect an application#qzwef for their accounts after importing the blueprint export a blueprint you can export a blueprint of the {{scenario singular lowercase}} as a json file to export a blueprint click {{scenario plural}} in the left sidebar choose an existing {{scenario singular lowercase}} , or click + create a new scenario , if you need to create the {{scenario singular lowercase}} first if it's a new {{scenario singular lowercase}} , add modules and https //help make com/module settings if it's an existing scenario, check that all of them are set up correctly in the upper right corner of the scenario builder, click the three dots > export blueprint once exported, the blueprint downloads to your device as a json file the file is typically named after your {{scenario singular lowercase}} for example if your {{scenario singular lowercase}} 's name is "new prospect notification", the file will be called new prospect notifcation blueprint json if the {{scenario singular lowercase}} has a default "new scenario" name, make names the file after the modules in the {{scenario singular lowercase}} , e g , integration google forms, google sheets blueprint json you can now share this file with other make users or keep it for your own future use import a blueprint we recommend creating a new {{scenario singular lowercase}} and importing the blueprint there if you import a blueprint while editing another {{scenario singular lowercase}} that hasn't been saved, all the changes in that {{scenario singular lowercase}} will be lost you can import a blueprint of the {{scenario singular lowercase}} saved in json format to import a blueprint in the upper right corner of the scenario builder, click the three dots > import blueprint click choose file, select the blueprint file in json format, and click save the imported {{scenario singular lowercase}} will appear in the {{scenario singular}} builder you can now configure your own account connections, make any necessary edits to the {{scenario singular lowercase}} , schedule it, and click the save icon 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 singular lowercase}} 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 c opy the blueprint to the clipboard, click the three dots > c opy blueprint to clipboard i n the upper right corner of the scenario builder to paste the blueprint into another scenario in make create a new scenario or open an existing one right click anywhere on the scenario canvas 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 singular lowercase}} , schedule it, and click the save icon check out the 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