---
title: "Add transform"
method: POST
path: "/pipeline/{pipeline_id}/transform"
tags: ["Pipeline Nodes"]
---

# Add transform

`POST /pipeline/{pipeline_id}/transform`

Add a transform to a pipeline

## Path parameters

- `pipeline_id` string, uuid, required

## Request body

- object
  - `type` 'filter' | 'sample' | 'drop-fields' | 'parse' | 'parse-sequentially' | 'route' | 'stringify' | 'compact-fields' | 'flatten-fields' | 'dedupe' | 'encrypt-fields' | 'decrypt-fields' | 'js-script' | 'unroll' | 'vrl' | 'reduce' | 'map-fields' | 'metrics-tag-cardinality-limit' | 'aggregate' | 'event-to-metric' | 'clustering' | 'redact' | 'throttle' | 'set-timestamp' | 'data-profiler' | 'replace' | 'trace-sampling', required
  - `deploy_type` 'saas' | 'local'
  - `title` string, nullable
  - `description` string, nullable
  - `user_config` object, required
  - `inputs` string[] — A list of inputs for the given transform. Typically this is empty when creating a new transform via the UI, but is leveraged by the terraform provider when managing pipeline state.

## Response `200`

Default Response

---

[API](https://skmtc.net/mezmo/apis/pipeline-api.md) · [All operations](https://skmtc.net/mezmo/apis/pipeline-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mezmo/pipeline-api/revisions/fb2535545d90/schema)