pipe

In a config modifier schema, use pipe to stack the outcome of a previous keyword as the input of the next. The keywords need to exist at the same nesting level for the keywords to be evaluated in order.

Think of pipe like a data assembly line. Instead of running just one action, pipe takes the starting payload, runs the first action, takes the result of that action, and feeds it directly into the second action, and so on. This allows you to chain multiple transformations together in a specific sequence.

This keyword executes in the following order:

1. omit
2. constant
3. references
4. use
5. get
6. Mutually exclusive keywords at this level:
   • properties
   • if
   • concat
   • switch
   • pipe
   • merge
   • prefer
   • items
7. default
8. plugin

You can change VisitDateTime to ISO format.

1
{
2
  "Visit": {
3
    ...
4
    "VisitDateTime": "2025-06-11 00:00:00Z",
5
    ...
6
  }
7
}

1
$.Visit.VisitDateTime

1
pipe:
2
  - plugin:
3
      name: text
4
      action: split
5
      parameters:
6
        separator: Z
7
        getIndex: 0
8
  - plugin:
9
      name: date-time
10
      action: parse
11
      parameters:
12
        custom: yyyy-MM-dd HH:mm:ss
13
        timeZone: America/New_York

Based on this example config modifier schema, VisitDateTime is updated to ISO format.

1
{
2
  "Visit": {
3
    ...
4
    "VisitDateTime": "2025-06-11T00:00:00.000-04:00",
5
    ...
6
  }
7
}