MessyAPI

Workflows

A visual builder for POST /api/v1/process. Only the 38 operations the engine accepts for chaining are offered.

Templates:

Input data[]

Step 1Clean

Normalize phone numbers to E.164 format.

Output records + artifacts

Held in this tab only. Sent once to the MessyAPI API through our server; never stored or logged. Use a messy_test_ key while experimenting.

Execution result

Run the workflow to see records, per-step results, artifacts and usage.

JSON representation

{
  "data": [
    {
      "name": "Ana Souza",
      "email": "ANA@example.com ",
      "phone": "(555) 123-4567",
      "city": "Austin"
    },
    {
      "name": "Ben Ito",
      "email": "ben@example",
      "phone": "555.987.6543",
      "city": ""
    }
  ],
  "steps": [
    {
      "operation": "normalize-phone",
      "options": {
        "field": "phone",
        "default_country_code": "1"
      }
    }
  ]
}

Generated API request

curl -X POST https://messyapi.com/api/v1/process \
  -H "Authorization: Bearer $MESSYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "data": [
    {
      "name": "Ana Souza",
      "email": "ANA@example.com ",
      "phone": "(555) 123-4567",
      "city": "Austin"
    },
    {
      "name": "Ben Ito",
      "email": "ben@example",
      "phone": "555.987.6543",
      "city": ""
    }
  ],
  "steps": [
    {
      "operation": "normalize-phone",
      "options": {
        "field": "phone",
        "default_country_code": "1"
      }
    }
  ]
}'

Saving workflows as project pipelines needs the existing pipelines API to be connected. Cost: Σ records_in × each operation's weight.