Pipeline: Basic Concepts

Description

Pipelines are designed to handle submissions across any channel. Can be configured in JSON.

• There is a set of elements that process data (pipes).
• Each element has an input and outputs. Their format has been determined.
• If the output type of one element is equal to the input of another, they can be connected in a pipeline.
• Inside the pipe, you can access the data and results of the pipe's action through keywords. The syntax is described in detail here.
• In each element, data entering the pipe is accessible through the $in keyword, and data entering the pipeline is available through $origin.`

A list of all available pipes with a description of their configuration can be found here.

Pipeline example:

[
  {
    "id": 1,
    "type": "packer",
    "params": {
      "type": "JSON"
    },
    "outs": {
      "success": 2
    }
  },
  {
    "id": 2,
    "type": "http_requester",
    "params": {
      "timeout": 10,
      "content_type": "JSON",
      "success_codes": [200, 202]
    },
    "outs": {
      "success": 3,
      "error": 4
    }
  },
  {
    "id": 3,
    "type": "event",
    "params": {
      "name": "mydeliv",
      "event": {
        "send_message_id": "$origin.send_message_id"
      }
    }
  },
  {
    "id": 4,
    "type": "event",
    "params": {
      "name": "myundeliv",
      "event": {
        "send_message_id": "$origin.send_message_id",
        "message": "$error.code $error.message"
      }
    }
  }
]