Skip to main content

Documentation Index

Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt

Use this file to discover all available pages before exploring further.

When something doesn’t look right, the first question is usually: is this me, Flowella, or Meta? This page tells you where to look for each.

​
Meta WhatsApp Business Platform

Most “messages not sending” or “delays” issues turn out to be Meta-side incidents. Check first: If Meta is reporting an active incident, sends will retry once the platform recovers — there is nothing to fix on the Flowella side.

​
Flowella

If Meta looks healthy and Flowella itself appears down or sluggish, in-app notifications are our primary signal. Open Notifications (or the bell icon) and look for Operational category notifications — we use these to broadcast incidents and maintenance windows that affect your org. See Notifications. You can also subscribe to operational events by email under Settings → Notifications.

​
HubSpot

If Flowella is healthy but HubSpot-specific actions are failing: A HubSpot incident will surface in Flowella as failed workflow actions or a disconnected integration banner on Settings → HubSpot.

​
Your integration

If neither platform is reporting an incident:
  • For API issues, check the response body — Flowella returns a structured error envelope. See API introduction.
  • For outbound webhooks that aren’t firing, check the delivery log under Settings → Webhooks. See Webhooks.
  • For HubSpot workflow failures, check the workflow’s action history in HubSpot. See HubSpot sync failures.

​
Reporting an incident to Flowella

If you believe Flowella is having an incident that isn’t reflected in your notifications, contact support with:
  • Your organisation name
  • A timestamp range (UTC) when you first noticed the issue
  • A description of what’s broken (with a screenshot if possible)
We’ll respond on the channel you contacted us on and update affected orgs via in-app notifications and email.