Workflows

Overview

Workflows are the heart of alerting and automation in upti.my. When an incident condition creates an incident, workflows take over and handle everything that happens next: where notifications go, how messages are formatted, which teams get paged, and what enrichment data is attached. You build all of this with a visual drag-and-drop flow builder.

Each workflow is a directed graph of nodes connected by edges. Data flows from a trigger node through optional processing nodes (conditions, delays, enrichment, HTTP requests) and terminates at one or more destination nodes (Slack, PagerDuty, email, webhooks, and more). You can branch, delay, loop, and transform data at every step. Workflows are managed through the dedicated API at workflows.upti.my.

Node Categories

The flow builder organizes nodes into three categories: triggers that start the workflow, processing nodes that enrich and shape the data, and destination nodes that deliver notifications and alerts.

Trigger Nodes (Entry Points)

Every workflow begins with exactly one trigger node. The trigger defines when and why the workflow executes. upti.my supports seven trigger types.

Processing Nodes (Middle)

Processing nodes sit between the trigger and destinations. They let you add logic, delays, data transformations, and external API calls to your workflow. You can chain multiple processing nodes together and create branches for complex scenarios.

Example: Escalation Chain

A common pattern is to notify a Slack channel immediately, then wait 10 minutes. If the incident is still open, escalate to PagerDuty. This requires a Condition node after the Delay to check whether the incident has been resolved.

{
  "name": "Production Escalation",
  "trigger": {
    "type": "healthcheck_status_changed",
    "filter": { "tags": ["production"], "to_status": "down" }
  },
  "nodes": [
    { "id": "notify_slack", "type": "slack", "channel": "#incidents" },
    { "id": "wait", "type": "delay", "duration": "10m" },
    {
      "id": "check_resolved",
      "type": "condition",
      "expression": "incident.status != 'resolved'"
    },
    { "id": "escalate", "type": "pagerduty", "severity": "critical" }
  ]
}

Destination Nodes

Destination nodes deliver notifications and data to external services. Each workflow can have multiple destinations, and you can use Condition nodes to route different alerts to different channels based on severity, tags, or time of day. upti.my supports seven built-in destination types.

Slack

Send messages to any Slack channel or direct message. Configure a message template using variables from the workflow payload, and optionally use Slack Block Kit for rich formatting. Requires a Slack workspace connection via OAuth.

Discord

Post messages to Discord channels using incoming webhooks. Supports embed templates with custom title, description, color, and fields. Configure the webhook URL in the node settings.

Email

Send email notifications to one or more recipients. Configure the subject line and body using templates. Supports HTML email bodies for rich formatting. Emails are sent fromnotifications@upti.my.

Microsoft Teams

Post messages to Microsoft Teams channels using incoming webhooks. Supports Adaptive Card templates for rich, interactive messages with buttons and sections.

Telegram

Send messages to Telegram chats or groups. Configure the bot token and chat ID, then define a message template. Supports Markdown and HTML formatting modes.

PagerDuty

Create PagerDuty incidents with configurable routing key, severity level (critical, error, warning, info), and summary. upti.my sends Events API v2 payloads, so incidents appear in your PagerDuty service with full context.

Custom Webhook

Send HTTP requests to any URL. Configure the HTTP method (GET, POST, PUT, PATCH), custom headers, and a JSON body template. This is the most flexible destination, allowing you to integrate with any service that has an HTTP API.

{
  "type": "custom_webhook",
  "url": "https://api.example.com/incidents",
  "method": "POST",
  "headers": {
    "Authorization": "Bearer {{ secrets.EXAMPLE_API_KEY }}",
    "Content-Type": "application/json"
  },
  "body": {
    "title": "{{ incident.title }}",
    "severity": "{{ incident.severity }}",
    "check_name": "{{ healthcheck.name }}",
    "status_url": "{{ incident.status_page_url }}"
  }
}

Workflow API

All workflow operations are available through the REST API at workflows.upti.my. You can create, update, delete, and trigger workflows programmatically. The API accepts JSON payloads and returns standard HTTP status codes.

curl -X GET https://workflows.upti.my/api/v1/workflows \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

Best Practices

• Start simple. Build a single trigger-to-destination workflow before adding processing nodes.
• Use the Rate Limit node to prevent notification floods during major outages.
• Test workflows with the Manual Trigger before connecting them to live alerts.
• Use Condition nodes to route critical alerts to PagerDuty and low-severity alerts to Slack.
• Keep escalation delays reasonable. A 5 to 15 minute delay before escalation gives on-call engineers time to respond.
• Use Transform Data nodes to enrich payloads with context before sending to external services.
• Review workflow execution logs regularly to identify failures or misconfigured nodes.