Docs / Contact / services/creating-services

Creating Services

Build services with validation rules to enforce data quality for your entities.

Create a New Service

1. Navigate to Services in the sidebar
2. Click Create Service
3. Provide a name for the service (e.g., "Temperature Sensor", "Motion Detector")
4. Add validation rules for each expected field
5. Save the service

Adding Validation Rules

Each saved rule reads back as Field · Operator · Value; the builder below adds another.

Each rule consists of:

• Field -- The path to the field in the message data (e.g., temperature, location.lat)
• Operator -- The comparison to perform (see Validation Rules)
• Value -- The expected value or range

A service holds one or more dynamic actions. Each dynamic action targets a kind of message (by name) and carries its own rules, optional requiredFields, and tags. Rules live inside a dynamic action; a top-level rules array is not part of the service shape and is ignored.

Example: Weather Station

JSON Example

{
  "name": "Weather Station",
  "dynamicActions": [
    {
      "name": "message:weather:reading",
      "requiredFields": ["temperature", "humidity"],
      "rules": [
        { "field": "temperature", "operator": "between", "value": [-50, 60], "message": "Temperature out of range" },
        { "field": "humidity", "operator": "between", "value": [0, 100], "message": "Humidity out of range" },
        { "field": "pressure", "operator": "between", "value": [300, 1100], "message": "Pressure out of range" },
        { "field": "station_id", "operator": "startsWith", "value": "WS-", "message": "Station ID must start with WS-" }
      ],
      "tags": ["weather-invalid"]
    }
  ]
}

Per dynamic action:

• name: identifies the action (a message:type:action naming convention is conventional but not enforced).
• requiredFields: fields that must be present in the message data; a missing one is recorded as a failure.
• rules: the field-level checks (see Validation Rules).
• tags: tags injected onto the message when this action's validation fails, so flows can route failed messages to specific connectors.

Assigning a Service to an Entity

1. Navigate to Entities
2. Edit the entity
3. Select the service from the Service dropdown
4. Save

All subsequent messages from that entity will be validated against the service's rules.

Editing a Service

1. Navigate to Services
2. Click the service name to open its detail page
3. Modify rules as needed
4. Save

Deleting a Service

1. Navigate to Services
2. Click Delete on the service
3. Confirm the deletion

Entities that were using the deleted service will fall back to the default service (if configured) or accept messages without validation.

Next Steps

• Validation Rules -- Full operator reference

← Back to Contact docs