Triggers
Start workflows manually, on a schedule, through a webhook or after an app event.
4 min readUpdated
Triggers
Start workflows manually, on a schedule, through a webhook or after an app event.
Use Triggers as a clearly defined step in an anymize workflow.
Alle Seiten in diesem Bereich
Manual Trigger nodeStarts the workflow when you click Run. Your JSON input is passed through unchanged. Following steps read its fields directly from $json, for example $json.message. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Webhook nodeStarts the workflow when an HTTP request hits your webhook URL. Body, headers, query parameters and path parameters are passed through as output, perfect for integrations with Zapier, Make, Slack buttons or your own apps. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.MCP Server nodeExpose this workflow as an MCP server. Dock tools (HTTP Request, knowledge base, Outlook, …), external MCP clients like Claude Desktop or Cursor list and call them via the MCP URL. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Chat nodeKicks 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.Schedule nodeKicks off the workflow at fixed times or in intervals, e.g. every hour, weekdays at 09:00, or on the 1st of each month. Multiple rules possible. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Telegram · New update nodeStarts the workflow for new messages, commands, channel posts, or button clicks received by your Telegram bot. The secure bot webhook is configured automatically in Production. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Anymize: Project created nodeStarts the workflow as soon as a new project is created, optionally only once an instruction and/or memory is set too. Starts exactly once per project, as soon as all conditions are met. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Anymize: Knowledge base created nodeStarts the workflow as soon as a new knowledge base is created. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Anymize: Knowledge base ready nodeStarts the workflow when a knowledge base has enough processed documents, by default only once processing has fully completed. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Klartext: Transcript ready nodeStarts the workflow as soon as a Klartext recording is transcribed, even before a summary exists. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Klartext: Summary ready nodeStarts the workflow as soon as the AI summary of a Klartext meeting is ready. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Anymize: Chat created nodeStarts the workflow as soon as a new chat is created, optionally only within a specific project. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Anymize: Document processed nodeStarts the workflow as soon as a document, text or URL has finished processing, including completed anonymizations. Optionally only for anonymizations or only on failures. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Outlook · New email nodeKicks off the workflow as soon as a new email arrives in the inbox. The workflow waits a short grace period (10 s) before it fires, so you can still delete an accidentally sent email before automation kicks in. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.Nextcloud · New/changed file nodeKicks off the workflow as soon as a file is added or changed in a watched Nextcloud folder. Anymize waits a short grace period so the upload is finished before the workflow fires. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.