Skip to main content

Apply blueprint

Apply blueprint deploys a blueprint to the target account. Every component in the blueprint is created or updated on that account. The apply runs asynchronously, so the automation continues immediately without waiting for it to finish. This action is available on account-scoped triggers.

info

This action is still labelled Apply account template in the automation builder, and the activity it logs is still called Account template applied. Both are being renamed to match the rest of Blueprints. Existing automations keep working either way.

How it works​

  1. The automation reaches the step with an account in scope
  2. You select the blueprint to deploy
  3. The step triggers the deployment asynchronously
  4. The automation continues to the next step immediately — deployment happens in the background

The blueprint's current version is the one applied. To deploy a different version, use Make v{N} current on the blueprint's Version history tab first.

Set up the action​

  1. Open the automation builder and add a new step
  2. Under Advanced, select Apply blueprint
  3. Configure the field:
FieldRequiredDescription
BlueprintYesThe blueprint to deploy to the account. Select from your available blueprints.
tip

Use data passing for dynamic blueprint selection, so you can choose different blueprints based on trigger data or earlier step outputs.

Outputs​

This action produces no outputs available to downstream steps.

Tips​

  • Deployment is asynchronous. The automation does not wait for the blueprint to finish. If downstream steps depend on resources the blueprint creates, such as AI employees or automations, add a Delay step to allow time for deployment.
  • Check the result on the blueprint. The Applied accounts tab shows whether the apply succeeded, which version landed, and per-component errors when it failed.