Open app

DocumentationWorkflowsTriggers

Chat node

Kicks off the workflow from an anymize chat. The user's message lands as input in the workflow, and the result goes back as the assistant's reply. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Kicks off the workflow from an anymize chat. The user's message lands as input in the workflow, and the result goes back as the assistant's reply.

Use Chat as a clearly defined step in an anymize workflow.

  • Starts a new workflow run.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Chat from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Chat has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
Display name in chatHow the workflow shows up in the chat tool picker. Empty = workflow name.Standard
Description in chatShown as a hint in the chat so users know when to trigger this workflow.Standard
Fields from the chat agentConfigure this value in the node panel.Standard

Inputs and outputs

InputMeaningType
StandardThis trigger does not require an input.JSON
OutputMeaningType
messageThe message the user sent in the chat.text
chat_idID of the conversation, for tracing or memory lookups.text
user_idanymize user ID of the caller.text
attachmentsUploaded files (name, MIME, optional Base64).json
historyLast N messages as context (see `history_window`).json

Example and test run

Outlook inbox summary: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "message": "Was ist heute in meinem Posteingang los?",
  "chat_id": "demo-conv-1",
  "user_id": "dev-42",
  "attachments": [],
  "history": []
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Workflow does not start: activate it and check the trigger's test and production mode.

Related articles