diff --git a/source/_docs/blueprint/schema.markdown b/source/_docs/blueprint/schema.markdown
index a0e7c06a129..c514467a495 100644
--- a/source/_docs/blueprint/schema.markdown
+++ b/source/_docs/blueprint/schema.markdown
@@ -96,7 +96,7 @@ a default value and also provide a [selector](/docs/blueprint/selectors/) that
 ensures a matching input field in the user interface.
 
 Each input field can be referred to, outside of the blueprint metadata, using
-the `!input` custom tag.
+the `!input` custom YAML tag.
 
 The following example shows a minimal blueprint with a single input:
 
@@ -117,6 +117,19 @@ was used in the user interface, a text input field would be shown to the user.
 
 A blueprint can have as many inputs as you like.
 
+### Blueprint inputs in templates
+
+The inputs are available as custom YAML tags, but not as template variables.
+To use a blueprint input in a template, it first needs to be exposed as either
+a [script level variable](/integrations/script/#-configuration-variables) or in 
+a [variable script step](/docs/scripts/#variables).
+
+```yaml
+variables:
+  # Make input my_input available as a script level variable
+  my_input: !input my_input
+```
+
 ## Example blueprints
 
 The [built-in blueprints][blueprint-built-in]