FlowPulse

Workflow observability

Know when your automations run, fail, or go quiet.

FlowPulse is the run ledger for n8n, Make, Zapier, and custom stacks—one API for success and failure, a single place to see history, reports, and alerts.

Start freeView integration guide

Works with the tools you already use

FlowPulse

Dashboard

Create workflowGet API key

Total workflows

3

Runs (24h)

115

Failed runs (24h)

54

Success rate (24h)

53.04%

Workflows with failures
3 need attention

Clone leads from HubSpot to Airtable

Last failed 9h ago

37 failures

Lead Enrichment

Last failed 9h ago

12 failures

Delete old leads

Last failed 9h ago

5 failures
View all failed runs →
Recent runs
  • Lead Enrichment
    failed9h ago
  • Delete old leads
    success9h ago
  • Lead Enrichment
    failed10h ago
  • Clone leads from HubSpot to Airtable
    success11h ago
  • Lead Enrichment
    success12h ago
  • Delete old leads
    failed14h ago
  • Nightly reconcile
    success1d ago
  • Webhook fan-out
    success1d ago
View all runs →

Silence is the hardest failure mode

When an automation stops running, most platforms won’t shout about it. You notice when it’s too late—missed handoffs, stale data, angry customers.

  • Failures hide in success-only monitoring—if you only hear about errors, you still miss “nothing ran.”

  • Execution history is scattered across n8n, Make, Zapier, and cron—no single SLA across tools.

  • Run-level truth is enough to act: did it execute, did it succeed, how long did it take—plus IDs to jump back to the source system.

Three steps. Minutes, not weeks.

  1. Define workflows in FlowPulse

    Create workflows that mirror your real automations. FlowPulse tracks them by stable IDs—rename tools on your side without breaking reporting.

  2. Send success and failure at the boundary

    Call the ingest API from the end of your success path and your failure path. Use your ingestion key—same pattern for n8n HTTP modules, Make webhooks, Zapier, or code.

    POST /api/v1/ingest/run-success
X-API-Key: fp_…

  3. Watch runs, reports, and alerts

    See run history, failure trends, and success rates. Add alert rules for failures, thresholds, durations, and no-run detection—delivered to your destinations.

Everything you need at run level

FlowPulse is optimized for fast instrumentation: one execution is one run, with the context you need to debug in your automation tool.

  • Success and failure

    Record both outcomes explicitly—not only when something throws.

  • Stable workflow IDs

    Events reference FlowPulse workflow IDs so renames do not fragment history.

  • Runs and history

    Browse executions with status, timestamps, and metadata for context.

  • Reports

    Failure rates, error breakdowns, and trends over time—per workflow and source.

  • Alert rules

    Thresholds, rates, durations, and no-run detection—wired to your destinations.

  • Workspaces & keys

    Team-scoped workspaces with ingestion keys you control.

Built for the tools you already use

If it can call HTTP, it can report to FlowPulse. We document patterns for n8n, Make, and Zapier—plus any language that can POST JSON.

n8n
Make
Zapier
Custom HTTP

Read the integration guide

A calm command center

The same information architecture wherever you work: dashboard overview, workflows, runs, reports, and alerts.

  1. 01

    Dashboard

    At-a-glance health: workflows, run volume, failures, and recent activity across the last 24 hours.

    Dashboard

    Create workflowGet API key

    Workflows

    3

    Runs (24h)

    115

    Failed

    54

    Success

    53%

  2. 02

    Workflows

    Organize every automation you monitor; open a workflow for detail and recent runs.

    Workflows

    </>

    Send Played Tracks to Discord

    send-played-tracks-to-discord

    + Add description

    29 runs100% successLast: Apr 7, 03:54 AM

    Recent runs

    • success—03:54 AM
    • success—03:12 AM
    • success—02:40 AM
    • success—01:58 AM
    • success—01:20 AM

  3. 03

    Reports

    See failure rate, error breakdowns, and trends—filter by time range and drill into what changed.

    Reports

    7d30d

    Failure rate

    All workflowsTop errors

  4. 04

    Alerts

    Rules for run status, rates, durations, and silence—delivered to the destinations you configure.

    Rules

    • Failure rate > 5% (24h)
    • No run in 6h
    • Duration > 120s

    Destinations

    • #ops-alerts
    • on-call@…

Built for operators and builders

  • Teams who rely on scheduled and event-driven workflows for revenue, ops, or customer experience.
  • Agencies managing many client workflows who need a single place to see health across tools.
  • Platform and backend engineers wiring AI agents, jobs, and glue code—who want run-level truth without tracing overhead.

Simple plans that scale with usage

Start free today—no credit card required. Paid tiers with higher limits and team features are coming soon; you'll be able to upgrade from workspace settings.

Heads upPaid checkout isn't live yet—ship on Free today; paid upgrades will show in the app when billing goes live.

Start here

Free

$0forever

Build and try FlowPulse on real traffic.

  • Up to 3 workflows
  • 1 alert rule
  • 1,000 billable ingests per month (UTC)
  • 3-day run log retention
Sign Up

No credit card required to start.

Paid plans — coming soon

Higher limits and paid checkout are on the way. Get started on Free—no card required.

Start free instead

Paid plans — coming soon

Higher limits and paid checkout are on the way. Get started on Free—no card required.

Start free instead

FAQ

Do I have to refactor my whole automation?

No. You add HTTP calls at the end of your success and failure paths—or the closest equivalent in your platform. That’s usually one node per path.

Is this a replacement for n8n / Make / Zapier?

No. FlowPulse observes runs. You keep building automations where you already build them.

What’s the difference between “failed” and “no run”?

A failed run is an execution that reported failure. No-run detection means an expected schedule or rate did not happen—so you catch silence, not just errors.

How is my data isolated?

Data is organized in workspaces. Ingestion uses API keys scoped to your workspace.

What should I send with each run?

At minimum: your FlowPulse workflow identifier. When available, add timestamps, duration, external execution IDs, and source platform—so you can jump straight to the native execution in your tool.

Ship with confidence—not guesswork

Create a workspace, add your first workflow, and send your first event in minutes.

Get startedLog in