The AI Prompt node

The AI Prompt node makes a single-turn call to a language model and writes the result as the node's output. It is the simplest of the two AI nodes: one prompt in, one answer out, with no tools and no multi-turn conversation. This article is for workspace users with the Admin role or higher who build workflows in the Designer.

• What the Node Does
• Configuration Fields
• Grounding on Knowledge
• Usage Credits

What the Node Does

Add an AI Prompt node from the AI section of the palette. When the step runs, AutomationAI sends your prompt — and an optional system message — to the model and captures the response. This is a single request and reply: the node does not call tools or carry on a conversation across turns. For a goal-directed node that reasons and uses tools, use the Agent node instead.

Configuration Fields

• promptTemplate — the prompt sent to the model. It supports {{ }} binding expressions, so you can fold in values from earlier nodes (see the article on passing data between nodes).
• systemMessage — an optional system message that frames how the model should respond
• maxTokens — the maximum length of the response, from 1 to 32768 tokens (default 1024)
• outputKey — the field name the response is written under in the node's output (default text)

You can also define explicit parameters bindings that the prompt template references. After the step runs, later nodes read the result at nodes.<id>.output.<outputKey>.

Grounding on Knowledge

You can ground an AI Prompt node on your knowledge base so the model answers with your own documents as context. In the node's grounding section, attach one or more Knowledge folders or documents; each appears as a chip you can remove. When the step runs, AutomationAI recalls the most relevant passages from the attached knowledge and supplies them to the model along with your prompt. For the full picture, see the article on grounding agents and AI Prompt nodes on knowledge.

Usage Credits

The AI Prompt node calls a language model, so each run consumes Usage Credits based on the tokens used. See the article on understanding Usage Credits and billing for how tokens convert to Credits.