Routes

Table of contents

  1. Name
  2. Endpoint
  3. Rule & Pipeline (JSON)

Name

Friendly name for a route

Endpoint

Select pre-defined Endpoint.

Rule & Pipeline (JSON)

Both rule and pipeline defined using JSON for now.

Schema defines both Rules and a Pipeline.

Default schema pre-filled for new routes (see below). map.generic_json pipeline transforms email into default deterministic shape.

Pipeline reminders:

  • pipeline.steps must contain at least one step.
  • Exactly one map.* step must exist.
  • The map.* step must be the final step.
  • Chat mappers use provider-specific destination arguments such as channel for Slack and chat_id for Telegram.
{
  "rule": {
    "to_contains": [],
    "from_domains": [],
    "subject_contains": [],
    "headers_equals": {}
  },
  "pipeline": {
    "steps": [
      {
        "name": "map.generic_json",
        "args": {}
      }
    ]
  }
}

Table of contents