Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maadify.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What prompt templates do

Prompt templates are reusable system prompts for sub-agents. Use them to standardize instructions, insert runtime variables, and keep a version history as your prompts change.
Prompt Templates page showing searchable template cards and the Create New Prompt Template button
If you edit the current version instead of creating a new version, every sub-agent that uses that template receives the change.

​
Browse prompt templates

Open Prompt Templates from the sidebar. The page lists the latest version of each available template as a card. Each card shows:
  • Version: the active version number.
  • System: a badge for built-in, read-only templates that are available to all tenants.
  • Name: the template name.
  • Description: a short summary. Hover to view longer descriptions.
  • Last Updated: the most recent update time.
  • Tags: labels that help you group related templates.
  • View Content: a hover preview of the template content.
Use Search prompt templates to filter by name or keyword. Press Enter or click Search. If there are more results than fit on one page, use the pagination controls below the grid.
The Create New Prompt Template button appears only when your role includes the prompt_templates.create permission.

​
Create a prompt template

1

Open the create dialog

Select Create New Prompt Template. The Prompt Template dialog opens on the Current tab.
2

Name the template

Enter a Template Name. Names are required.
3

Add a description and tags

Write a Description that explains when to use the template. Add tags if you want to group templates by workflow, team, or use case.
4

Write the template content

Add the system prompt in Template Content. You can write plain Markdown and insert variables with Jinja syntax.
5

Save the template

Select Save. New templates start at version 0.1.
Prompt Template dialog showing template name, version, description, tags, and template content editor
Template Name, Description, and Template Content are required before you can save.

​
Edit a prompt template

Click a template card to open it. Templates owned by your tenant open in edit mode when your role includes prompt_templates.update. System templates and templates owned by another tenant open in view-only mode. When you edit a tenant-owned template, use Create New Version to decide how the save behaves:
  • Turn Create New Version on to keep the selected version in history and save your changes as the next version.
  • Turn Create New Version off to update the existing version directly.
Version numbers increase by 0.1 when you create a new version. For example, version 0.1 becomes 0.2.
Create a new version for meaningful prompt changes. Edit the existing version only when you are correcting a typo or making a small safe change.

​
Insert variables

Prompt templates support Jinja-style variables inside double braces. 
{{ input.question }}
{{ system.current_datetime }}
{{ tool_model.gmail_12.send_email_34.input_schema }}
Use the variable autocomplete in the editor or the Template Content help menu to find available variables. The available variables depend on the prompt context and the tools connected to the sub-agent or flow. Common variable groups include:
  • Inputs: runtime inputs such as input.question, input.history, input.files, and input.element_ids.
  • Trigger Inputs: values passed by the trigger that started the workflow.
  • System: system values such as system.current_datetime.
  • Tool Models: tool input and output schemas or examples, such as tool_model.{tool}.input_schema.
  • Tool Configs: configured tool properties, such as tool_config.{tool}.{property}.
  • Context variables: outputs from trigger tools, execute tools, code execution stubs, or structured-output sub-agents.
Use dot notation for nested values and numeric indexes for arrays. For example, {{ order_lookup.items.0.id }} reads the first item ID.

​
Preview example inputs

Use View Input Example to inspect the sample JSON available to the template. Use Render Example Inputs to render the template with those example values. This helps you catch missing variables or formatting issues before saving.
Prompt Template dialog showing the View Input Example popover and rendered template preview

​
Review version history

Open the History tab in the dialog to review previous versions for the selected template. Select a version card to preview it. The preview area includes:
  • Preview: renders the selected version as Markdown.
  • Diff: compares the current content with the selected version.
  • Use this version: copies the selected version back into the editor. Saving after this creates or updates the active template based on your permissions and Create New Version setting.
Prompt Template History tab showing version cards, preview, diff, and Use this version button

​
Delete a prompt template

If your role includes prompt_templates.delete, a Delete button appears for templates owned by your tenant. Select Delete, then confirm the deletion in the confirmation dialog.
Delete only templates that are no longer used by sub-agents. Deleted templates are removed from the template list.

​
Example prompt template

agent_summary.txt
You are the operations coordinator.

Current time: {{ system.current_datetime }}
User request: {{ input.question }}

Summarize the most recent order activity from {{ order_lookup.orders }}.
If any orders are blocked, list the reason and recommended next step.
Return the result as a short paragraph and a bullet list.