Scenario sharing

scenario sharing allows you to create a public scenario page that you can share with others via a link or post on social media anyone with the link can view the public scenario page or log in to make and create a copy of a shared scenario in their make account and then edit or use it unlike with blueprints , you don’t need to export, import, re export, and copy scenario blueprints after any change the link always shows the latest saved version of the scenario sharing scenarios through a link is also faster and more flexible than sharing them through templates in particular, when you simply want to demonstrate an automation, viewers don't have to log in or sign up for a make account to see it create a link to share scenario to create a link for sharing a scenario create a new scenario or open an existing one if it’s a newly created scenario, you will need to save the scenario before sharing it in the upper right corner of the scenario builder, click share for an existing scenario, you can also click share in the scenario diagram in the share scenario window, you will see the scenario name and the thumbnail (preview image) this thumbnail is created automatically see how to edit it scenario sharing /#edit thumbnail switch on the public scenario page toggle you can now copy the link and share it with anyone customize public details to configure how your scenario appears on the public scenario page in the upper right corner of the scenario builder, click share in the share scenario window, click customize public details there you can edit thumbnail hover over the image and click edit thumbnail you will see the scenario use zoom and drag to set the part that should be displayed in the thumbnail click save at the top of the screen to apply changes, or cancel to revert to the default thumbnail this thumbnail is attached to the link when it’s shared on social media t he thumbnail is not automatically adjusted when you make changes to the shared scenario to reflect the changes, go to the share scenario window, click customize public details, and update the thumbnail in the edit thumbnail section add title enter a title (max 40 characters) that will be displayed on the public scenario page it can differ from the scenario's name add description provide a brief explanation (max 260 characters) of what the scenario does this description will appear under the title on the public scenario page add additional information include the details (max 2000 characters) that viewers should know to make the scenario work, e g , how to set up an app, configure modules, or establish connections this will be displayed in the additional information section on the public scenario page check author's details check the author and avatar section that will be displayed on the public scenario page this section includes author’s name this is the name of the make user who last saved the scenario thus, it can differ from the person who initially created it you can change how your name is displayed in the profile settings of your make account author's avatar this is the picture set on gravatar com for the author's email address used in the make account if you don't have a picture set or want to change the current one, you need to do it via gravatar com when finished, click save changes share scenario via social media or email you can also share scenarios directly on social media platforms or via email in the upper right corner of the scenario builder, click share in the share scenario window, click share via social click the required platform (email, linkedin, facebook, or x) you'll need to complete the authorization process for the selected social media platform after that, you'll be redirected to the new post creation page or the new email draft page the post should have automatically attached a scenario preview, containing scenario thumbnail scenario title (as specified by scenario metadata) scenario description, if added check sharing status when a scenario is shared, you will see a blue shared label next to the scenario name in the scenario builder or scenario diagram you can also see a blue shared label next to the scenario name in the scenarios folder, if it's currently shared a shared link is dynamic viewers always see the latest saved version of the scenario you must save changes for them to appear in the shared scenario unsaved changes are indicated by an orange shared label next to the scenario name preview public scenario page to preview the public scenario page in the upper right corner of the scenario builder, click share in the share scenario window, click preview public page disable scenario sharing to stop sharing the scenario in the upper right corner of the scenario builder or scenario diagram, click share switch off the public scenario page toggle the link will no longer work anyone who accessed the scenario while the public page link was enabled will still keep their copy if you enable scenario sharing again, the link will remain the same anyone who had access to the previously shared public page will be able to see the most up to date version again public scenario page users who get the link or see a scenario shared on social media can click it and see the public scenario page this is a view only, shareable page that includes title description interactive scenario preview additional information author’s name and avatar as a viewer, you can click the +use the scenario button on that page if you are logged in to make, a copy of the scenario will be created in your account if you are not logged in to make, you will be prompted to sign in after signing in, a copy of that scenario will be created in your account if you have multiple organizations and/or teams in your make account, the scenario will be added to the last organization > team you've opened (or which is currently selected) what is included in a scenario shared via a link modules module settings (with mapped values, but without connections) metadata scenario notes what is not included in a scenario shared via a link api keys, passwords, and other details used to create a connection subscenarios , make ai agents , data stores , and data structures are shared as empty modules custom and community apps may not be displayed in a shared scenario if they haven't been approved and made installable by the users’ organization if the shared scenario includes apps that require installation, users without admin permissions in their organization will see a warning prompting them to contact their organization’s admin to proceed if your scenario includes subscenarios, make ai agents, data stores, data structures, and custom or community apps, you’ll see a warning before sharing click continue sharing to share the scenario as it is those who copy and use a shared scenario have to create their own connections and provide credentials for all the apps in the scenario if the scenario includes subscenarios, ask a creator to share them separately, or create them manually, and connect afterward create their own ai agents recreate the data stores and data structures manually install custom and community apps themselves as a scenario creator, you can use the additional information field to explain how to handle elements that aren’t shared with the scenario you can also add scenario notes when preparing a scenario for sharing to help users quickly tailor the scenario to their use case