Blueprints are the foundation for most Vessels. They contain the design specifications needed to start building solutions for your organization. As such, they live at the organization level and can be used for any Project. They can either be built by Shipyard staff (as part of the Blueprint Library) or created by users in your organization.

These Blueprints provide a way for technical users to create a reusable piece of code with organization-specific logic. When using a Blueprint, users are only required to provide key inputs needed for the Vessel to work correctly. All code and requirements are abstracted away from the end user.

All Blueprints are built using Code. You must select a supported language and provide the necessary code, requirements, and packages necessary to make the Blueprint usable. Additionally, you can create Blueprint Variables that users fill out on the Inputs tab when they are setting up a new Vessel.

As a Blueprint author or editor, you are in charge of writing the code that runs for the users of your Blueprint. You can update and manage the underlying code, making updates in bulk that can affect 100s of scripts.


Creating a Blueprint

When creating a Blueprint, you must always provide the following elements:

You may also optionally provide these elements:

Building a Vessel

When creating a Vessel with a Blueprint, you must always provide the following elements:

  1. Inputs (if any are required)

You may also optionally provide these elements:

  1. Triggers


  1. Code for a Blueprint must have an adequate level of error handling and validation because it relies on user input.

  2. Notifications cannot be set for all Vessels that are built from a Blueprint.

Learn More