Communication#

How Whoobe talks to other systems and how other systems talk to Whoobe: Integrations (Whoobe calls your systems), Automations (forms start flows), the Client Hub (your applications call Whoobe), and mail. The common rule is that credentials stay on the server (credentials stay on the server).

1. Integrations: Whoobe calls your systems#

Document	What it covers
Integrations guide	Endpoints and routes, OpenAPI import, presets, visual binding, filters, security, limits, troubleshooting
API Gateway security	How the credentials are stored and protected
Brevo integration	Send a page or snippet as a Brevo campaign

2. Automations: forms start flows#

Document	What it covers
Marketing automation	A form hands its submission to Activepieces, n8n or any webhook; the page reacts to the answer
Automations architecture	What Whoobe does, what the engine does, what travels between them
Node-RED	The flow editor on the same machine as Whoobe and not exposed: the preset, the wizard, the function node that writes back, developing and deploying a flow
Object events	Tell a service when a Data Object is created, changed, published or deleted: subscriptions, payload, delivery log, signature, loops
Forms with file upload	Files from visitors: checks, private storage, limits
Why no engine of our own	The decision and its costs

3. Client Hub: your applications call Whoobe#

Document	What it covers
API clients guide	Register an application, key or identity-provider token, scopes for integration routes, published data and automations, calls, errors, limits
Client access without user accounts	The decision and its costs
API reference	/client/v1 and the administration routes

4. Mail#

Document	What it covers
Outgoing mail	SMTP and HTTP mail providers, per-website settings, the mail log, templates

In the dashboard: Data & Communication > Integrations, API clients, Automations, Data bindings, Outgoing Mail.