Skip to content
LatidoFlow
Open navigation
Create account

Getting started

Go from a new workspace to verified operational evidence.

Choose the signal that matches the work, verify it through the real execution path, then add alerting and customer communication without mixing setup with proof.

1. Choose what LatidoFlow should observe

Active check

Uptime monitor

LatidoFlow calls a public HTTPS endpoint on a schedule and evaluates status, body, or JSON outcome rules.

Passive signal

Heartbeat monitor

A cron job, worker, queue job, or external automation reports its own completion and optional business outcome.

2. Verify the first real signal

  1. 1

    Create the account

    Register with email and password or a supported Google identity, verify the email address, and confirm the workspace timezone in Settings.

  2. 2

    Create one monitor

    Use the dedicated Uptime monitors or Heartbeats screen. Start with one business-critical path and an explicit success condition.

  3. 3

    Exercise the real path

    Queue a real uptime probe or let the actual recurring workload send its completion or lifecycle event. A setup simulation is useful for configuration checks, but it is not production evidence.

  4. 4

    Read back the result

    Open the monitor detail page and confirm the run, outcome, timestamp, and current health match the execution you observed.

  5. 5

    Add response routing

    Create a notification channel, simulate its rule, send a test alert, and enable it only after the provider accepts the test.

3. Use the setup path that fits your team

Product UI

Create monitors, respond to incidents, configure channels, publish status updates, and manage workspace access.

Set up monitors

REST API

Synchronize definitions and send runtime evidence from any language with an HTTP client.

Send signals

AI agent

Connect the hosted MCP server for customer-authorized management, or let an agent integrate the REST contract into application code.

Connect an agent

Healthchecks.io import

Preview a Management API v3 JSON export, apply the import, verify fresh signals, and retain a conservative rollback path.

Import safely

Know what has actually been proved

Configured

A monitor or integration definition exists.

Instrumented

The application code or external system can emit the intended signal.

Active

LatidoFlow accepted a real signal from that execution path.

Operational

The signal, alert route, and response workflow have all been verified.