Unify Logo Footer.svg
Unify Automations
Logo
Call LLM Model with Options

Call LLM Model with Options

Logo

2 mins READ

Call LLM Model with Options sends a prompt to a language model of your choice and returns the model's response. You select the model — Claude, GPT, Gemini, and others — when building the automation, and pass the prompt, an optional system instruction, and any call settings as inputs at run time. Use this node when you need a configurable, single model call inside a larger automation flow.

Overview

This node is the current, supported way to invoke a language model in AgentKit. An older operation named Call LLM Model (without "with Options") is deprecated — do not build new automations on it, and migrate any existing ones. The "with options" version provides full control over model selection and call parameters. Because the model is chosen at build time rather than per run, automations that need different models for different cases should branch and use a separate node per path.

call_llm-1-final_1.png
call_llm-1-final_1.png

Input

Field

Description

Required*

Model

The language model to call. Selected when building the automation (Claude, GPT, Gemini, and others) and fixed for the run — it cannot be switched at run time.

Yes

Prompt

The user-turn input sent to the model. Accepts static text or dynamic values from prior steps.

Yes

System Prompt

System-level instructions that establish the model's behavior, persona, or constraints for this call.

No

Temperature

Controls response randomness. Higher values produce more varied output; lower values produce more deterministic responses.

No

Max Tokens

Maximum number of tokens in the model's response. Caps output length for the call.

No

Call Options

Additional model-specific settings passed at invocation time. Available options depend on the selected model.

No

Call_llm-2-final_1.png
Call_llm-2-final_1.png

Output

The node returns two values:

  • Response — the model's generated text, ready to use in downstream steps.

  • Usage — token usage details for the call, including prompt tokens, completion tokens, and total tokens.

Notes

  • The model is fixed at build time. If your automation needs different models for different scenarios, use a branch and a separate Call LLM Model with Options node for each path.

  • The deprecated Call LLM Model (without "with Options") should not be used for new automations. Existing automations using it should be migrated to this node.

  • Available call options vary by model — consult the model's documentation for supported parameters.

  • Dynamic values from earlier steps can be interpolated into the Prompt and System Prompt fields.

FAQs

Can I switch which model is called at run time?

No. The model is selected when you build the automation and is fixed for the node. To use different models conditionally, branch your automation and configure a separate node for each model.

What happened to Call LLM Model (without "with Options")?

It is deprecated. New automations should use Call LLM Model with Options exclusively. If you have automations still using the older node, migrate them to avoid relying on a deprecated operation.

Does the node support streaming responses?

The node returns the complete response when the model finishes. Use downstream steps to process or display the output.