Omni Webhook MCP Server

omni-webhook

Omni schedule and alert deliveries POST export files or link payloads to ingest storage. Each delivery reflects whichever published dashboard, chart, format, and filters were configured upstream — tabular columns are not fixed across schedules.

What upstream deliveries look like

Omni scheduled and alert webhooks commonly arrive as:

• Multipart file upload — CSV, PDF, PNG, or XLSX attached directly; CSV becomes export.rows, other formats may only expose export.text or binary metadata.
• Link JSON — a compact wrapper such as { "url": "..." } when the export is hosted elsewhere; storage fetches the linked file bytes when reachable.
• Zip-wrapped CSV — dashboards with multiple queries may bundle several .csv files; the first CSV inside the archive is unpacked for tabular preview.

Alert deliveries fire only when threshold conditions match — a quiet history may mean the alert did not trigger, not that ingest is broken. Schedule deliveries follow the cadence configured upstream (often hourly at most; runs can lag ~15 minutes).

First moves

1. Latest report — default for "what did the scheduled export say".
2. Report freshness — check source.captured_at and source.filename before quoting figures.
3. Recent reports — compare runs, spot duplicate filenames, or find a specific delivery date.
4. One report by id — after listing, when the user names a specific run.

Response shape

• source — capture time, filename, format, connection purpose.
• export.rows — parsed CSV preview when tabular; may truncate with rows_truncated.
• export.text — full body when rows truncate or the file is not tabular.
• export.json — parsed JSON when the stored payload was JSON.

PDF, PNG, and XLSX attachments may store with limited tabular preview — prefer export.text or note binary content.

Operational order

1. Start with the latest report — do not guess a report id.
2. If captured_at is older than expected, say so — upstream sends on their schedule (often hourly at most; delivery times can lag by ~15 minutes).
3. List recent reports only for history, duplicate suspicion, or explicit compare-by-date asks.
4. Read ## This connection in the skill supplement for property-specific column or field notes.

Gotchas

• Read-only — cannot trigger a new upstream send or change schedule settings from here.
• Variable columns — do not assume fixed KPI names; read headers from the latest rows or This connection notes.
• Link-only deliveries — upstream may POST a JSON wrapper with a dashboard link instead of a file; storage holds fetched file bytes when available.
• Zip-wrapped CSV — dashboards with multiple queries may arrive as a ZIP; unpacked automatically when a CSV is inside.
• Format varies — the same dashboard can be scheduled as CSV, PDF, PNG, or XLSX; inspect source.filename and format before interpreting content.
• Alerts vs schedules — alert deliveries fire only when conditions match; gaps in history may mean the alert did not trigger.
• Each delivery is one report — latest is the newest capture, not a merged history.