Skip to content
Routario Docs

Incoming email

Trigger · Stable

Fire when an email arrives at your workspace inbox address, optionally filtered by recipient (To).

Receives inbound email. In the hosted product, mail sent to your workspace address (@mail.routario.com) is routed here automatically; self-hosted instances point their email provider at the workspace inbox. Use the recipient (match_to) filter to scope a flow to specific To: addresses. The body and any attachments are saved to Memory. Context keys: from (sender), to (list), cc, subject, body (plain text), html, attachments (list of {filename, mime, size, ref}), and source_doc_id.

When to use

Section titled “When to use”

Use when users or external parties email a dedicated address to kick off a workflow — e.g. forwarding an invoice PDF to trigger OCR, or routing support emails into a triage flow. The from, subject, body, and attachments keys are available immediately to downstream steps.

When not to use

Section titled “When not to use”

If the signal arrives via HTTP (not email), use Webhook. If you only want to send an outbound email (not receive one), use the Send email step instead. For WhatsApp messages use Incoming WhatsApp. Heads-up: a run from this trigger has no signed-in user, so {{ user.* }} and {{ actor.* }} are empty. Bind any recipient or owner — a send_email to, a deal owner_actor_id, a task assigned_to — to a concrete email or actor_id, never {{ user.* }}; or collect it at run time with an Ask-a-person step.

Inputs

Section titled “Inputs”

match_to

Section titled “match_to”

string · optional

Only fire when the recipient address matches this fnmatch pattern, e.g. invoices@* or *@acme.cz. Leave empty to fire on every inbound email.

Example: invoices@*

Auto-generated from the skill registry (load_skills()). Do not edit by hand.