tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

How to Set Up FlowMattic Cloud: Webhooks That Retry, Schedules on Time

FlowMattic Cloud: a Stripe webhook goes to hooks.flowmattic.com, which retries and delivers it to the WordPress site where the workflow runs.

FlowMattic Cloud is the service that stays awake when your WordPress site cannot. It receives webhooks for your site and keeps retrying for about five days if the site is down, wakes your site the moment a schedule, delay or other timing is due, whether or not anyone visits, and hosts managed FlowMattic Tables. It is an optional add-on with a Free plan to start, and you can set up FlowMattic Cloud in one click from wp-admin.

Your workflows do not move. FlowMattic, the automation plugin for WordPress, still runs every workflow on your own server; FlowMattic Cloud only delivers the events and wakes the site when a timing is due, and without it FlowMattic works as it always has. This guide covers connecting the account, Cloud Webhooks with retry and replay, the Scheduler, downtime alerts, plans and usage, and the details that matter in production.

What is FlowMattic Cloud?

FlowMattic Cloud is one account for three services: Cloud Webhooks, the Scheduler and FlowMattic Tables. You manage it from FlowMattic → FlowMattic Cloud in wp-admin, a screen only administrators can open. The screen sums it up: an optional add-on that you can start on the Free plan, and when you hit a limit you are told, never billed for overage.

It solves two problems a self-hosted site has on its own. A webhook sent while your site is slow, updating or offline is lost unless the sender retries. And WordPress cron only runs when someone loads a page, so a schedule on a quiet site fires late. Cloud handles the always-on part, and the work still happens on your server.

How to set up FlowMattic Cloud

Connect the Free account

Open the FlowMattic Cloud screen and press Connect for free. The site starts on the Free plan, registered with your FlowMattic license, and no card is needed. Connecting switches on the Scheduler; Cloud Webhooks stay off until you choose them on a Webhook trigger. Reconnecting later updates the site address Cloud has on file, so a site moved to a new domain keeps receiving webhooks.

FlowMattic Cloud admin screen showing the plan hero and service usage tiles
The FlowMattic Cloud screen with the plan, the Cloud Webhooks, Scheduler and FlowMattic Tables tiles, and the Upgrade and Docs actions.

Cloud Webhooks: retries and replay

Open a workflow’s Webhook trigger and find the Delivery section. Change Deliver via from “This site (direct)” to “FlowMattic Cloud — retries for about 5 days, replay failed events”. Press Generate Cloud webhook URL to create the hooks.flowmattic.com address before you save, so you can copy it into the sending app and capture a test request. The panel also shows where Cloud forwards each event: your site’s real webhook URL, custom slug included.

From then on, senders post to Cloud. Cloud stores each event and delivers it to your site, retrying for about five days if the site does not answer. When the site comes back after an outage, the events that waited are delivered straight away instead of at their next retry. Each delivery is signed by Cloud and verified by your site. A sender’s own signature, from Stripe, Slack or Paddle, is checked against the time the webhook first reached Cloud, so a retried delivery still passes the sender’s replay window. If Cloud retries an event your site already ran, the site answers it as a duplicate and does not run the workflow twice.

The Cloud Webhooks card on the Cloud screen lists every hook with its URL, its workflow, deliveries in the last 30 days, and counts of queued, retrying, failed and held events. Events opens a table with each event’s status (Queued, Delivered, Retrying, Failed, Held or Dropped), when it was received and how many attempts it took. A failed event has a Replay button that queues it for delivery again, for as long as your plan’s replay window allows. Load older events pages back through the list. Delivered events are counted, not stored; failed and held events stay until they are replayed or expire.

FlowMattic Cloud screen cards for the Scheduler switch, Cloud Webhooks hooks and Downtime alerts
The Scheduler, Cloud Webhooks and Downtime alerts cards on the FlowMattic Cloud screen.

Scheduler: Cloud wakes your site on time

The Scheduler is on as soon as the site is connected. Your schedules, Delays, API Polling, booking reminders and follow-ups, approval timeouts, connection token refreshes and clean-ups stay on your site, in FlowMattic’s own job table. Whenever that list changes, the site tells Cloud when the next timing is due, and at that moment Cloud sends a signed request that wakes the site to run everything due. Only the time of the next timing goes to Cloud, never the workflow. Timings run on the minute on the Free plan and to the second on paid plans, with no limit on schedules on any plan.

The switch on the Scheduler card is Wake this site from FlowMattic Cloud; the same choice is in Settings as Wake This Site For Timings. Switched off, or on a site without Cloud, the timings run through WordPress cron as before, which also checks the same list every minute as a backup. The card lists your Scheduled workflows with each timing, its Next run and Last run. Check Cloud can reach this site tests the connection, and Re-sync with Cloud registers the site again straight away. Each scheduled run carries fire_id, scheduled_for, fired_at, timezone and source (cloud or wp_cron) in its trigger data, so Task History shows when it was due and what started it.

If Cloud stops waking the site for 10 minutes, you see a notice in wp-admin and get an email, the timings keep running through WordPress cron, and a second email follows once Cloud reaches the site again. With or without Cloud, weekly and monthly schedules run on the chosen day only, and times follow the site time zone across daylight-saving changes.

Downtime alerts

With Email me when this site can’t be reached on, Cloud emails you when it cannot deliver to your site for 30 minutes, reminds you once a day for up to four days, and emails once more when deliveries go through again. Alerts go to your account email, or to the Send alerts to address. Send a test email checks the route. The Scheduler’s wakes count too, so a site that only uses the Scheduler is covered. Webhooks keep queuing the whole time, whether alerts are on or off.

Plans, usage and billing

The top of the Cloud screen shows your plan (Free, Starter, Pro or Business) and three service tiles. Cloud Webhooks shows events used this period against your plan’s allowance, the number of hooks and how long failed events are kept. Scheduler shows how many workflows run on a schedule, how many times Cloud woke the site this period, and whether timings are woken by FlowMattic Cloud or running on WordPress cron. FlowMattic Tables shows whether a managed database is included in your plan; Tables comes with the paid plans, from Starter, and its records and writes are shown on the FlowMattic Tables screen.

One subscription covers all three services on the site. Upgrade plan (Change plan on a paid plan) opens the plan cards, upgrades apply straight away with a prorated charge, and Manage billing opens the billing portal. When your account is eligible, paid plans start with a 7-day free trial, and choosing one lets you pick the data region (United States, Europe or India) where your Tables database lives. More on each plan is on the FlowMattic Cloud page.

PlanPriceCloud WebhooksReplay failed eventsSchedulerFlowMattic Tables
FreeFree1,000 events a month1 dayUnlimited schedules, on the minuteNot included
Starter$5 a month or $49 a year25,000 events a month4 daysUnlimited schedules, to the second100,000 records, 250,000 writes a month
Pro$15 a month or $149 a year250,000 events a month15 daysUnlimited schedules, to the second500,000 records, 2,000,000 writes a month
Business$39 a month or $399 a year1,000,000 events a month30 daysUnlimited schedules, to the second2,000,000 records, 10,000,000 writes a month

Key settings at a glance

SettingWhereWhat it does
Connect for freeCloud screenCreates the Free account for this site, tied to your license.
Deliver viaWebhook trigger, DeliveryThis site (direct) or Cloud, with retries and replay.
Generate Cloud webhook URLWebhook trigger, DeliveryCreates the hooks.flowmattic.com address before you save.
Wake this site from FlowMattic CloudCloud screen, or Settings as Wake This Site For TimingsTurn it on and Cloud wakes the site when a timing is due. Off, timings run on WordPress cron.
Email me when this site can’t be reachedCloud screen, Downtime alertsTurns downtime emails on or off; Send alerts to sets the address.
Release held eventsCloud screen noticeDelivers events held at your plan’s cap against the remaining allowance.

Use cases

Never lose a payment webhook during maintenance

A store or SaaS site points its Stripe webhook at the Cloud URL. When the site is down for an update, the payment events wait in Cloud and arrive as soon as it is back, each passing Stripe’s signature check.

Flow: Stripe → Cloud → Webhook trigger → update the order or account → Send Email

Send client reports at 9:00 on Monday, every Monday

An agency’s weekly client reports run from small, quiet sites where WordPress cron used to run them late. With Cloud waking the site, the Every Week schedule runs at 9:00 in the site’s time zone.

Flow: Schedule (Every Week, Monday 9:00, Cloud wakes the site) → collect figures → PDF Template Builder → Send Email

Catch leads while the site is being migrated

A marketing team’s form and ad tools post leads to a Cloud URL. During a hosting move the leads queue in Cloud; after the move, Reconnect updates the address and the queued leads are delivered.

Flow: Lead form webhook → Cloud → Webhook trigger → CRM → Slack

Know when the site is down before customers do

Internal ops sets Send alerts to the on-call inbox. If Cloud cannot reach the site for 30 minutes, the alert arrives, and a second email confirms when deliveries resume.

Flow: Delivery fails for 30 minutes → downtime alert email → site back → recovery email

Replay a webhook after fixing the workflow

Support finds a helpdesk event that failed because the site rejected it during a plugin conflict. After the fix, they open the hook’s Events on the Cloud screen and press Replay.

Flow: Helpdesk webhook → Cloud (Failed) → Replay → Webhook trigger → ticket workflow

Test webhooks on a local or staging site

A developer registers a tunnel address with the flowmattic_cloud_site_url filter, so Cloud forwards events to a local copy of the site while the workflow is being built.

Flow: Sending app → Cloud → tunnel → local Webhook trigger

Tips and gotchas

  • Use the Permalink Based webhook URLs. Deliver via FlowMattic Cloud needs the /webhook/capture/ URL structure. If Settings uses REST API Based URLs, switch Webhook URL Structure and save the workflow again.
  • Cloud delivery is set on the main trigger. In a multi-trigger workflow, additional webhook triggers do not show the Delivery setting.
  • Imports start direct. A workflow imported from a file, a shared link or the template library has its webhook delivery reset to direct, so an import never registers a Cloud hook by itself.
  • Replay before the window closes. Each plan keeps failed events for a set number of days, counted after the retries end. The Cloud Webhooks tile shows how long yours are kept.
  • Plan caps hold, they do not bill. Webhook events over your allowance are held, and the screen offers Release held events or an upgrade. The Scheduler has no cap on schedules on any plan.
  • Reconnect if Cloud requests cannot be verified. If the screen says Cloud has not issued a callback secret, press Reconnect. Check Cloud can reach this site confirms the round trip.
  • The Cloud module. The screen and the Deliver via option come from the FlowMattic Cloud module in Core Modules. A trigger already delivering through Cloud keeps its Delivery setting even if the module is turned off, so there is always a way back to direct. Your timings carry on through WordPress cron.

Related features

  • Webhook trigger: capture, custom slugs and signature checks, direct or through Cloud.
  • Scheduler: every schedule type, and how they behave on Cloud.
  • FlowMattic Tables: the managed database that comes with the paid Cloud plans.

FAQ

Is FlowMattic Cloud free?

FlowMattic Cloud is an optional add-on with a Free plan, and every license can start on it: 1,000 Cloud Webhooks events a month and the Scheduler with unlimited schedules, on the minute. Paid plans, from $5 a month, add capacity, to-the-second timings and FlowMattic Tables. Plan details are on the FlowMattic Cloud page.

Do my workflows run on FlowMattic’s servers?

No. Workflows, credentials and run logs stay on your WordPress site. Cloud receives webhooks and wakes your site when a timing is due, and the workflow runs there.

What happens to webhooks when my site is down?

With Deliver via set to FlowMattic Cloud, Cloud keeps each event and retries delivery for about five days. When the site is back, waiting events are delivered straight away, and anything that still failed can be replayed from the Cloud screen.

Why do WordPress scheduled workflows run late?

WordPress cron only runs when someone loads a page, so on a quiet site a schedule waits for the next visit. Connect FlowMattic Cloud and turn on Wake this site from FlowMattic Cloud, and Cloud wakes your site when each timing is due: on the minute on the Free plan, to the second on paid plans.

Every FlowMattic license can start on the Free Cloud plan. Choose a FlowMattic plan, then set up FlowMattic Cloud from its screen in wp-admin.

More from the blog