Integrations

Integrations are the building blocks that triggers and steps are made of. Each integration does one thing well — call an AI model, send an email, run a database query, listen for incoming webhooks. You compose automations by combining them.

This page is the catalog. Click any entry for the full configuration reference and recommendations.

Triggers vs. Actions

Family	Where it appears	What it does
Triggers	The first slot of every automation	Decide when the automation runs. One or more per workflow; an agent has exactly one (Chat or Form).
Actions	Every step in the body of the automation	Do the actual work — send, fetch, query, write, generate. Many per automation.

A trigger never appears as a step, and an action never appears as a trigger. The editor only offers integrations that fit the slot you are filling.

AI & Knowledge

For prompting models, building agentic loops, and searching your knowledge bases.

• AI action — the workhorse: let an AI model summarise, extract, classify or write — optionally with look-ups in your knowledge bases. (Replaces the earlier LLM Prompt.)
• Knowledge Query — search a knowledge base from inside a workflow.
• LLM Data Anonymizer — mask sensitive parts of a text before it leaves your network.
• LLM Data Deanonymizer — restore the masked parts afterwards.

Communication

• Send email — send, reply in the thread or save a draft; Markdown text, signature, attachments.
• Send E-Mail (old) — deprecated, replaced by Send email.

Documents

• Excel — create, fill, extend or read workbooks; from data, Markdown tables, a template or with AI.
• Word — create, fill, edit or read documents; from Markdown, your company template or with AI.

Data & System

• HTTP Request — call any HTTP/HTTPS endpoint.
• Database Query — read or write with SQL (PostgreSQL, MySQL, SQL Server, SQLite)
• Store file (server folder / WebDAV) — save a file to a folder, network drive or WebDAV (Nextcloud, NAS); convert to Word, Excel or CSV; copy, move, delete.
• File Writer — write or append text to a file on the server.
• Request approval — pause the run until a person decides.
• Script Execution — run a bash or PowerShell script.

Time and Event Triggers

• Scheduled Task (Cron) — run at fixed times.
• HTTP Webhook — run when an external system posts to a URL.
• Email received — run when a new email arrives in an IMAP mailbox, with attachments as files.
• E-Mail Inbox (old) — deprecated, replaced by Email received.
• Filesystem Watcher — run when a file appears in a directory.
• Records changed (server folder / WebDAV) — run when rows are added, changed or removed in a CSV, Excel or XML file; the changes arrive as Markdown tables.
• Database Listener — run when a SQL query returns new, changed or removed rows.
• Cloud Storage (MinIO) — run when a new object appears in a bucket.
• Calendar (ICS) — run when an ICS feed lists a new event.
• Google Calendar — run on Google Calendar changes (OAuth).
• Agent tool — run when an agent calls the workflow as a tool; defines what the agent hands over.

Agent-only Triggers

These triggers only appear when the automation is of type Agent.

• Chat Input — the user starts the conversation by typing.
• Form Input — the user fills in a form first.

How to read an integration page

Every integration page follows the same structure:

• What it does — one sentence.
• What you configure — a table of every field, what it controls, and whether it is required.
• Example scenario — one concrete situation where this integration shines.
• Recommendations — what to do, what to watch, what to avoid.

If you are looking for a specific configuration field, the search bar at the top of the documentation usually finds it faster than scrolling.

What to do next

• Build something with these blocks: Create a New Automation.
• Understand the wiring between blocks: Core Concepts.