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.

Last updated: April 6, 2026

Privacy Policy

This policy describes how FlowPulse (“we”, “us”) handles personal information when you use our website (https://www.flowpulse.xyz) and the FlowPulse product (including the application and API). We aim to be straightforward: we collect what we need to run the service, protect it, and communicate with you.

Who we are

FlowPulse is operated by Philippe Mathew De Vera, an individual based in Philippines. For privacy-related requests, contact philmattdev@gmail.com.

What this policy applies to

It applies to information collected through this marketing site and through your use of the FlowPulse application, API, and related infrastructure (for example authentication, ingestion endpoints, and support communications).

Information we collect

Account and contact details. For example, email address and profile details you provide when you sign up or contact us.
Product and usage data. Data you (or your integrations) send to FlowPulse to make the product work—such as workflow identifiers, run status, timestamps, error details, and related metadata needed for observability. Avoid sending secrets or highly sensitive personal data in payloads unless you intend to.
Technical and security data. Such as IP address, device and browser type, approximate location derived from IP, diagnostic logs, and anti-abuse signals—used to operate, secure, and troubleshoot the service.
Cookies and similar technologies. We use cookies or local storage for authentication, preferences, and security. On this marketing site we use Google Analytics 4 (via Google Tag / gtag.js) and, when the site is hosted on Vercel, Vercel Web Analytics for aggregate page views and performance insight. You can control cookies through your browser settings and use Google’s opt-out tools where available.
Payment information. If you purchase a paid plan, payment processing is handled by a third-party processor (for example Stripe). We typically receive limited billing metadata—not your full card number—which the processor handles according to its own terms.

How we use information

We use personal information to:

Provide, maintain, and improve FlowPulse;
Authenticate users, prevent fraud and abuse, and protect security;
Communicate with you about the service (for example service messages and support);
Comply with law and enforce our terms;
Analyze reliability, performance, and marketing-site traffic in aggregate where helpful;

Legal bases (where they apply)

Depending on where you are located, privacy laws may require a “legal basis” for processing. Where applicable, we rely on: performing our contract with you; legitimate interests in running and securing the service (balanced against your rights); compliance with legal obligations; and, where required, your consent.

Sharing and subprocessors

We do not sell your personal information. We may share information with service providers who help us host infrastructure, process payments, send email, monitor uptime, measure site analytics (for example Google), or provide customer support—only as needed for them to perform services for us, and under appropriate safeguards. We may also disclose information if required by law, or to protect the rights, safety, and security of FlowPulse, our users, or the public.

International transfers

Your information may be processed in the Philippines and in other countries where our providers operate. If we transfer personal data across borders, we take steps designed to protect it consistent with this policy and applicable law.

Retention

We retain information for as long as your account is active and as needed to provide the service, comply with legal obligations, resolve disputes, and enforce our agreements. Retention periods can vary based on data type and configuration.

Security

We use reasonable administrative, technical, and organizational measures to protect personal information. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

Your choices and rights

Depending on your location, you may have rights to access, correct, delete, export, or restrict certain processing of your personal information, and to object to certain processing. You may also have the right to lodge a complaint with a supervisory authority. To make a request, email philmattdev@gmail.com. We may need to verify your request before responding.

Children

FlowPulse is not directed to children under 13 (or the minimum age required in your jurisdiction). If you believe we have collected information from a child, contact us and we will take appropriate steps.

Changes to this policy

We may update this policy from time to time. We will post the updated version on this page and update the “Last updated” date. If changes are material, we will provide additional notice when practical (for example by email or an in-product notice).

Contact

Questions about this policy: philmattdev@gmail.com