Templates
A headless template is a named container for one or more flows (plus profile configuration,
knowledge-base descriptors, and phone-number requirements) authored with {{field}} placeholders
instead of concrete values — the pattern that gets substituted per tenant when an
instance is created.
Authoring
Section titled “Authoring”From headless.v2.nairon.xyz → Templates, create a template and open its flow(s) in the graph
editor — this opens in template mode, which legalizes {{field}} tokens anywhere a normal flow
would expect a literal string, and disables Test/Publish (a template isn’t a runnable flow by
itself). As you type {{field_name}} tokens into node text, hook actions, or integration
configuration, the editor extracts them into the template’s field schema automatically.
Integration templates
Section titled “Integration templates”A template can also define integration templates — the same connect forms used for
integrations in the marketplace, but in “abstract mode”: {{field}}
placeholders instead of concrete secrets, substituted with each tenant’s own credentials when their
instance is materialized.
Status
Section titled “Status”A template moves through draft → published → archived. Only a published
version of a template can be used to create an instance.