Integrations

Connect any service that can call HTTP.

LatidoFlow works with cron hosts, workers, queues, notification senders, deployment scripts, CI jobs, and application frameworks. Start with direct HTTP calls, then use a package only when it saves setup time.

Use the heartbeat URL directly when a cron host only needs to report successful completion, or use the Monitor sync endpoint for CI, workers, custom deployment tooling, and framework-specific packages.

curl -fsS "https://www.latidoflow.com/heartbeat/{monitor_uuid}/{token}"
# or
curl -X POST "https://www.latidoflow.com/heartbeat/{monitor_uuid}/{token}"

curl -X POST https://www.latidoflow.com/api/v1/monitors/sync \
  -H "Authorization: Bearer ${LATIDOFLOW_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "project": {"name": "Billing App", "slug": "billing-app"},
    "environment": {"name": "Production", "slug": "production"},
    "monitors": [{
      "name": "Nightly invoice sync",
      "slug": "nightly-invoice-sync",
      "type": "scheduled",
      "cron_expression": "0 2 * * *",
      "grace_seconds": 900,
      "timeout_seconds": 3600,
      "metadata": {"source": "cron-host"}
    }]
  }'

Detect

Export service checks, queue names, job classes, webhook calls, and expected runtime windows from the monitored app.

Verify

Validate credentials and definition sync, then obtain execution proof from a non-synthetic ingested run.

Respond

Open incidents, route alerts, and publish status updates when jobs drift.

Optional Laravel detector kit

Laravel teams can install the package to read scheduler events from Illuminate\Console\Scheduling\Schedule, merge configured queue definitions, and post them to the Monitor sync endpoint with LATIDOFLOW_TOKEN.

composer require latidoflow/laravel
php artisan latidoflow:install
php artisan latidoflow:sync
php artisan latidoflow:verify

'latidoflow' => [
    'token' => env('LATIDOFLOW_TOKEN'),
    'sync_endpoint' => env('LATIDOFLOW_SYNC_ENDPOINT', 'https://www.latidoflow.com/api/v1/monitors/sync'),
    'queues' => [
        ['name' => 'Invoices queue', 'connection' => 'redis', 'queue' => 'invoices', 'job_class' => App\Jobs\SyncInvoices::class],
    ],
]

Monitoring as code

Monitor detail pages export YAML, PHP, and JSON config. Commit the file, verify it in CI, and import reviewed JSON or YAML back into LatidoFlow when schedules change.