Skip to main content
Make blueprints let you move or share a Make scenario as a JSON file. The file describes the scenario structure, modules, routes, filters, and mappings. The blueprint does not include a working BrowserAct connection or account credentials. After importing a blueprint, reconnect BrowserAct and any other apps before running or activating the scenario.

​
Import a Make Blueprint

  1. Log in to Make.
  2. Open Scenarios and create a new scenario.
  3. Open the scenario menu and select Import Blueprint.
Open Import Blueprint in Make
  1. Choose the JSON blueprint file and confirm the import.
Choose the Make blueprint JSON file
  1. Review the imported modules, routes, filters, and mapped inputs.
  2. Reconnect the BrowserAct module and any other applications used in the scenario.
  3. Select the Workflow that corresponds to your BrowserAct Bot and verify its inputs.
  4. Run the scenario once before activating it.

​
Export a Make Blueprint

  1. Open the Make scenario.
  2. Open the scenario menu and select Export Blueprint.
Open Export Blueprint in Make
  1. Save the JSON file.
Save the exported Make blueprint

​
Share the Blueprint

After exporting the JSON file, you can share it with teammates, clients, or the Make community. Recipients can import the file by following the import steps above. Before sharing a blueprint, review it for fixed values, test data, or other sensitive information. API keys and application credentials should never be added directly to the JSON file.

​
Tips

  • Review imported scenarios before activating them.
  • Reconnect BrowserAct, API keys, and third-party app accounts after import.
  • Check required input fields before running the scenario.
  • Use clear file names when saving blueprint files.
  • Add notes inside Make if the scenario will be shared with another user.
A Make blueprint is a Make scenario file, not a BrowserAct Bot export.