Start Workflows from Chat Message Ingress

The chat message workflow trigger, labeled When chat message received, starts a workflow when a message is sent to that workflow’s chat URL. It uses a generated endpoint ID and supports public-access and response-mode settings.

Screenshot to add: When chat message received trigger configuration showing public access and response mode settings

Configure the chat trigger

1. Open Agent Workflows and edit the workflow.
2. Add the When chat message received trigger node.
3. Keep the generated Chat endpoint ID. The plugin creates this unguessable ID when the trigger is added; it is hidden in the configuration.
4. Choose whether to enable Make chat publicly available. When disabled, requests require a logged-in user with permission to manage workflows. When enabled, anyone who has the URL can send messages.
5. Set the chat title, subtitle, input placeholder, and initial messages if you want to customize the chat interface.
6. Choose a Response mode. When last node finishes waits for the workflow run. Acknowledge immediately (queue run) is intended to acknowledge without waiting for the final node output; execution is queued when background execution is enabled and may run synchronously if that setting is disabled.
7. Connect the trigger to the next node, save the workflow, and test with a controlled message.

Chat request and payload

The REST route uses the dragaiw/v1/chat/{endpoint_id} path. The endpoint accepts POST requests containing JSON. The message can be provided as chatInput; the normalizer also recognizes chat_input, message, prompt, or text. It normalizes the message to chatInput and uses sessionId (or generates one if missing). The payload can also include action, metadata, and files.

Understand access and response behavior

• The endpoint must match an active workflow. If the workflow is inactive, the endpoint cannot accept the chat message for execution.
• Public access is off by default. Enable it only if the chat should accept messages from anyone who has the URL.
• The endpoint is rate-limited to 30 requests per minute per client IP and endpoint ID.
• Requests with an empty normalized chatInput are rejected.
• Test the endpoint and inspect the response before using it in a public or production workflow. Do not expose the endpoint ID unnecessarily.

Map the incoming message

Use the variable picker to map chatInput, sessionId, and any supported metadata into later nodes. The trigger’s sample payload can help you configure the workflow, but it is only sample data and does not verify a live chat submission.