FlowPulse

Workflow reliability monitoring

Know when a client automation quietly breaks.

Get alerted when a Zapier, Make, or n8n workflow never runs, fails, or takes longer than expected.

Sign upView Documentation

Missing runs, failed runs, and long run durations in one place.

FlowPulse

Dashboard

Total workflows

3

Runs (24h)

115

Failed runs (24h)

54

Success rate (24h)

53.04%

Recent alerts

  • No webhook runs detected for Stripe to CRM sync

    Missing runs for 2h

    Sent to Slack #client-alerts

    Critical

  • Lead enrichment failure rate exceeded threshold

    62% failed in last 30m

    Sent to Slack #automation-watch

    Warning

Workflows with failures

Clone leads from HubSpot to Airtable

Last failed 9h ago

37 failures

Recent runs

  • Lead Enrichment
    failed9h ago
  • Delete old leads
    success9h ago
3-step integration

Integrate with existing workflows in 3 steps

No rebuild. Just send events and configure alerts.

  1. Add two calls

    Send one event on success and one on failure.

  2. Verify events

    Run the workflow once and confirm events arrive.

  3. Turn on alerts

    Set failure, duration, and optional missing-run alerts.

View Documentation

The failure most teams miss is silence

Agencies and consultants do not lose trust because a workflow throws an obvious error. They lose trust when a workflow quietly stops delivering expected outcomes.

FlowPulse is focused on this: catch missing runs, long durations, and failed executions.

  • Missing runs are the expensive failures: a client workflow skips an expected run and nobody notices until downstream damage appears.

  • Long-running executions are easy to miss, but they often signal broken dependencies and delayed client outcomes.

  • Completed status is not enough: runs can report success while the expected result never happens.

Common alert patterns

Alert coverage for real production issues

These are common alert types teams start with. FlowPulse supports additional alert rules as your workflows scale.

  • 01

    Missing run alerts

    Define how often a workflow should run and get alerted when an expected run does not happen.

  • 02

    Long run duration alerts

    Set a run-duration threshold and get alerted when a completed run took longer than expected.

  • 03

    Run failure alerts

    Get immediate alerts when a workflow reports a failed execution so you can respond fast.

Integration-ready

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.

HTTP

n8n

HTTP Request node

HTTP

Make

HTTP module

HTTP

Zapier

Webhooks by Zapier

HTTP

Custom HTTP

Any client / language

Read the integration guide

Simple plans that scale with usage

Free plan is fully usable today. Paid plans unlock higher limits and retention as your run volume grows.

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.

MOST POPULAR

Pro

$20/ workspace / month

For teams shipping workflows every day.

  • Unlimited workflows
  • Unlimited alert rules
  • 20,000 billable ingests per month (UTC)
  • 14-day run log retention
Sign Up

Secure checkout. Taxes may apply based on your location.

Scale

$70/ workspace / month

Higher volume and longer history.

  • Unlimited workflows
  • Unlimited alert rules
  • 100,000+ billable ingests per month (UTC)
  • 30-day run log retention
Sign Up

Secure checkout. Taxes may apply based on your location.

FAQ

Who is this for right now?

Automation agencies, Zapier/Make consultants, freelancers managing client automations, and n8n builders with client-facing workflows.

Do I have to refactor my whole workflow?

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 Zapier, Make, or n8n?

No. FlowPulse tracks run events and alerts. You keep building and running automations in your existing tools.

What failures does FlowPulse catch?

Common cases include missing runs (expected run never happened), failed runs, and long run durations.

How does onboarding work?

Sign up, follow the docs, and connect one workflow first. Most teams can add the required HTTP calls and configure alert rules quickly.

How is pricing structured?

FlowPulse has a free tier and paid plans as workflow volume grows. You can review plan details from the pricing section.