Everstack
Getting StartedWorkflow StudioNode Reference

Node Reference

Available node types for building workflows.

Every node in Workflow Studio belongs to one of seven categories. This page documents each node type, what it does, its key configuration options, and its handle types.

Handles are the connection points on a node. Input handles accept data from upstream nodes. Output handles emit data to downstream nodes. Some nodes have multiple output handles for branching (for example, guardrail nodes produce both a pass and a block handle).

AI

LLM

Sends a prompt to a language model and returns the response.

ConfigDescription
ProviderWhich provider and model to use (e.g., OpenAI GPT-4, Anthropic Claude)
System promptThe system message sent with the request
User promptTemplate for the user message, supports variable interpolation from upstream handles
TemperatureSampling temperature for the model response
Max tokensMaximum tokens in the response
StreamingWhether to stream tokens as they arrive

Handles: One input (prompt variables), one output (model response).

Agent

Spawns an Everstack agent and waits for or streams its result. Use this when a step requires autonomous multi-turn reasoning with tool use rather than a single model call.

ConfigDescription
Agent definitionWhich agent configuration to use
Input messageThe message sent to the agent, supports variable interpolation
TimeoutMaximum time the agent is allowed to run
AsyncWhether to wait for completion or continue and check later

Handles: One input (message and context), one output (agent response).

Code

Function

Executes a registered Everstack function. Functions can run as webhook handlers, proxy handlers, or in isolated sandbox runtimes depending on their configuration.

ConfigDescription
FunctionWhich registered function to execute
Input mappingMap upstream handle values to function input parameters
TimeoutMaximum execution time

Handles: One input (function parameters), one output (function return value).

Integration

HTTP

Makes an HTTP request to an external API and returns the response. Use this for calling third-party services, internal APIs, or any REST endpoint.

ConfigDescription
MethodGET, POST, PUT, PATCH, DELETE
URLThe endpoint URL, supports variable interpolation
HeadersRequest headers, supports variable interpolation
BodyRequest body template for POST/PUT/PATCH
TimeoutMaximum time to wait for a response
RetryNumber of retries on failure

Handles: One input (request parameters), one output (response body, status code, headers).

Webhook

Defines an inbound webhook trigger point within the workflow. When the workflow is triggered by a webhook, this node receives the incoming request payload and makes it available to downstream nodes.

ConfigDescription
PathThe webhook path suffix
SecretShared secret for request signature verification
Method filterWhich HTTP methods to accept

Handles: No input handle (this is a trigger node), one output (request payload, headers, method).

Logic

Condition

Evaluates an expression and routes execution to one of two branches. This is how you build if/else logic in a workflow.

ConfigDescription
ExpressionThe condition to evaluate, supports variable references from upstream handles
OperatorComparison operator (equals, not equals, contains, greater than, less than, regex match, etc.)

Handles: One input (variables to evaluate), two outputs -- true and false. Connect downstream nodes to the appropriate output handle.

Loop

Iterates over a list or repeats a subgraph a fixed number of times. Each iteration passes the current item and index to the loop body.

ConfigDescription
Modefor-each (iterate over a list) or count (repeat N times)
SourceThe list variable to iterate over (for-each mode)
CountNumber of iterations (count mode)
Max parallelHow many iterations can run concurrently

Handles: One input (the list or context), one output (aggregated results from all iterations).

Transform

Applies a data transformation to reshape, filter, or map values between nodes. Use this when the output format of one node does not match the input format of the next.

ConfigDescription
ExpressionA transformation expression or template
Output formatExpected output shape (JSON schema or freeform)

Handles: One input (source data), one output (transformed data).

Safety

Input Guardrails

Runs input safety checks (PII detection, prompt injection prevention, content filtering) on data flowing through the workflow. Produces two output handles so you can route safe and blocked content differently.

ConfigDescription
ChecksWhich guardrail checks to enable (PII, prompt injection, content filter)
PII actionBlock or redact when PII is detected
SensitivityThreshold for content filtering (0.0 to 1.0)

Handles: One input (content to check), two outputs -- pass (content is safe, continues to next step) and block (violation detected, routes to error handling or alternative path).

See Input Guardrails for details on each check.

Output Guardrails

Runs output safety checks (jailbreak detection, toxicity filtering, code execution prevention) on model responses before they reach downstream nodes or the end user.

ConfigDescription
ChecksWhich output checks to enable (jailbreak, toxicity, code execution)
SensitivityThreshold for toxicity detection (0.0 to 1.0)

Handles: One input (model output to check), two outputs -- pass and block.

See Output Guardrails for details on each check.

Voice

TTS (Text-to-Speech)

Converts text to audio using a configured voice provider.

ConfigDescription
ProviderTTS provider and voice model
VoiceVoice selection or voice ID
SpeedPlayback speed multiplier
Output formatAudio format (mp3, wav, opus)

Handles: One input (text content), one output (audio data and metadata).

STT (Speech-to-Text)

Transcribes audio input to text using a configured speech recognition provider.

ConfigDescription
ProviderSTT provider and model
LanguageExpected language for transcription
TimestampsWhether to include word-level timestamps

Handles: One input (audio data), one output (transcribed text and metadata).

Voice Clone

Creates or uses a cloned voice profile for TTS synthesis. Combine with the TTS node for personalized voice output.

ConfigDescription
Source audioReference audio for voice cloning
Voice nameLabel for the cloned voice profile
ProviderVoice cloning provider

Handles: One input (reference audio or voice ID), one output (cloned voice profile for use by TTS nodes).

Data

Memory Query

Queries the Everstack memory layer to retrieve stored context, facts, or embeddings. Use this to give downstream LLM or Agent nodes access to relevant stored knowledge.

ConfigDescription
QueryThe search query, supports variable interpolation
LimitMaximum number of results to return
FilterOptional metadata filters to narrow results

Handles: One input (query parameters), one output (retrieved memory entries).

Memory Store

Writes data to the Everstack memory layer. Use this to persist outputs from earlier workflow steps for future retrieval.

ConfigDescription
ContentThe content to store, supports variable interpolation
MetadataKey-value metadata to attach to the memory entry

Handles: One input (content to store), one output (confirmation and stored entry ID).

Custom nodes

Beyond the built-in types, you can register custom node types by wrapping an Everstack function as a node. Custom nodes appear in the node palette alongside built-in types and follow the same handle and configuration conventions.

On this page