Integrations
Webhooks & Automation

Webhooks & Automation

Some tools can't be driven by the WordPress plugin — either they don't expose WordPress hooks (Bookly, Booknetic, BookingPress) or they live outside WordPress entirely. Every one of them can still reach FlowAlert, because they can all send an HTTP request.

This page is the step-by-step for connecting those tools. They all do the same thing under the hood: POST an event to the FlowAlert events endpoint. Once the event arrives, your routing rules, acknowledgements, and escalation policies treat it exactly like any other event.

Connecting Stripe or Shopify? You don't need the manual POST on this page — FlowAlert has a native, signature-verified receiver for each. You paste a FlowAlert URL into the provider and your signing secret into FlowAlert; no Zapier, no field mapping. See the Stripe and Shopify guides.

What you're pointing them at

EndpointPOST https://api.flowalert.io/v1/events
Auth headerX-Api-Key: fa_live_… (from Setup → API Keys)
Content typeapplication/json
Minimum bodyevent, title, body

A minimal payload:

{
  "event": "booking.created",
  "title": "New booking — Jordan Lee",
  "body": "Consultation · Today 3:30 PM",
  "priority": "HIGH"
}

See the REST API reference for the full field list (priority, detail, data, dedupeKey, requiresAck, link).

"Built-in webhook" is not the same as the one-click WordPress plugin. You're configuring the other tool's own webhook/HTTP step to point at FlowAlert. There's no code, but it's a few minutes of setup in that tool — not a single toggle.

Uncanny Automator

Add FlowAlert as the final action of any recipe, so any of Automator's triggers becomes a routed, accountable push notification.

Open your recipe

Edit (or create) the recipe whose trigger you want to alert on.

Add the webhook action

Add an action and choose Send data to a webhook (Automator's generic outbound webhook). Set:

  • Request method: POST
  • URL: https://api.flowalert.io/v1/events
  • Content type: application/json

Add the header

Add a request header X-Api-Key with your FlowAlert API key as the value.

Map the body fields

Add body fields event, title, body (and optionally priority). Use Automator tokens for the values — e.g. title = New lead: {{first_name}}.

Go live and test

Publish the recipe, fire the trigger once, and confirm the event in Dashboard → Alerts. Then create a routing rule for your event key.

WP Webhooks

WP Webhooks can POST any WordPress event to an external URL with no code.

Create a "Send Data" flow

In WP Webhooks → Send Data, create a new webhook for the WordPress trigger you care about.

Point it at FlowAlert

  • Webhook URL: https://api.flowalert.io/v1/events
  • HTTP method: POST
  • Add header X-Api-Key: fa_live_…

Map the payload

Map the trigger's data into event, title, and body (plus priority/data if you want). WP Webhooks lets you rename and template these fields in its own UI.

Test

Trigger the event and check Dashboard → Alerts, then add a routing rule.

SureTriggers / OttoKit

Add a FlowAlert webhook action to any workflow to inherit routing, acknowledgement, and escalation.

Add a Webhook action

In your workflow, add a Webhook / Custom App action set to POST.

Configure the request

  • URL: https://api.flowalert.io/v1/events
  • Header: X-Api-Key: fa_live_…
  • Body (JSON): event, title, body, optional priority — fill the values from earlier workflow steps.

Activate and test

Turn the workflow on, run it once, and confirm the event arrived.

Booknetic

Booknetic is closed-source and exposes no WordPress hooks, but it ships a Webhooks workflow action.

Open Booknetic workflows

Go to Booknetic → Settings → Workflows (or the Workflow tab) and add a workflow for the event you want — e.g. Appointment created.

Add a Webhook action

Add a Webhook action with:

  • Method: POST
  • URL: https://api.flowalert.io/v1/events
  • Header: X-Api-Key: fa_live_…

Map appointment fields

Map Booknetic's placeholders into the JSON body — event = booking.created, title = New booking — {customer_full_name}, body = {service_name} · {appointment_date} {start_time}.

Save and test

Book a test appointment and confirm the event, then create a booking.created routing rule.

Bookly

Bookly's core is fully encapsulated and provides no developer hooks, so there's no native plugin trigger to tap. Use Zapier instead (Bookly Pro includes a Zapier integration), or the REST API if you have a custom handler.

Create a Zap

Create a Zap with a Bookly trigger such as New Appointment.

Add the FlowAlert action

Add a FlowAlert → Send Alert action. See Zapier for connecting your API key.

Map the appointment

  • Event Key: booking.created
  • Title: New appointment — {{Customer Name}}
  • Body: {{Service}} · {{Date}} {{Time}}
  • Priority: HIGH

Turn it on

Publish the Zap and book a test appointment. The event lands in FlowAlert and routes like any other.

💡

No Zapier and no developer to call the REST API? Bookly can't be connected without one of those two paths — it simply doesn't expose the hooks a native integration would need.

Anything else

If a tool can send an authenticated HTTP POST, it can reach FlowAlert. For tools on Zapier use the Zapier app; for everything else, POST directly per the REST API reference.

WordPress PluginStripe