What are Blueprints#

To create and manage pre-configured Automations on behalf of users, partners can create Automation "Blueprints". Blueprints are useful when partners wish to create an experience where the user simply "enables" a predefined integration rather than creating their own custom workflows via the AutomationsManager component.

Identifying blueprints#

Blueprints consist of a blueprintKey, which uniquely identifies the Blueprint within the partner's Rollout implemenation, and parameters for customizing the form for creating and editing Automations.

Blueprint configuration#

Partners can specify the Trigger & Actions and map data between the two on behalf of users, as well as hide or disable fields pre-configured for the user, in order to provide a simpler user experience.

All required data (i.e. user credentials and reqiured inputs) must be provided by either the user or partner when the user "enables" the Blueprint in order to succesfully create an Automation.

Example usecase#

As an example, a partner can create a Blueprint titled "When a task is created in the partner app, create the same task in Asana", where the task name and due date are mapped on behalf of the user. To enable this Blueprint, the user simply has to connect their Asana account and select which Asana workspace and project the task should be created in.

BlueprintEnabler Component#

Blueprints are enabled through the BlueprintEnabler component, which takes the blueprintKey and automation form customization options as props. See the UI Component docs for more detials.