algos crm.
CRM Documentation
The same product docs available in the dashboard—guides for setup, architecture, modules, and day-to-day use.
Website Forms
Current (supported) path — website lead webhook
Independent of the Channels UI “Website Forms” provider. Server-to-server POST creates a tenant lead.
Configure
WEBSITE_LEAD_WEBHOOK_SECRET=long-random-secret
[email protected]
WEBSITE_LEAD_RATE_LIMIT=10
Endpoint
POST /webhooks/leads/website
Middleware: website-lead-webhook + throttle website-leads. CSRF exempt.
Never put the webhook secret in browser JavaScript. Call from your backend only.
Demo UI
Users with website_lead.demo can open Administration → Website Lead Demo to exercise the flow.
vs Channels Generic Webhook
| Website lead webhook | Generic Webhook channel | |
|---|---|---|
| Config | .env secret |
Per-connection secret |
| Multi-tenant routing | Implementation-specific / shared endpoint | Per-company UUID URL |
| UI connection row | No | Yes under Channels |
For new multi-tenant form backends, prefer Generic Webhook per company unless you standardize on the dedicated website endpoint.
Planned — Website Forms channel builder
Listed in config/channels.php as website_form but no channel adapter is registered yet.
Planned capabilities:
- Form builder / embed snippets per tenant
- First-class Channels connection + health
- Unified event log with other providers
Until then, the provider may appear in the connect dropdown as Adapter coming soon.