Let your own systems write into the CRM, on your terms.
WebToCRM exposes endpoints that external sites, forms and applications can use to create, read, update or delete records — scoped to the entities, operations, fields and domains you allow.
What it does
- Endpoints you define: Each configuration targets one entity type and enables only the operations you choose: Create, Read, Update, Delete or Customer 360.
- Field allow-lists: Only the fields you explicitly permit are accepted, and callers must use the exact field names you select. Nothing else gets written.
- Domain restrictions: Restrict submissions to named domains, wildcard subdomains, or leave open. Success and error redirect URLs can be configured per endpoint.
- Rate limiting with visibility: Set thresholds per minute, hour and day plus burst limits and block durations. A dashboard reports requests, blocked and suspicious traffic, with violation logs, IP reputation and an org whitelist.
- Feeds automation: An inbound write can create a record in a custom object, which in turn triggers a Flow — so an external event can drive a whole workflow.
Specifics
- CRUD plus Customer 360 per endpoint
- Explicit field allow-lists
- Exact-domain and wildcard restrictions
- Per-minute, hour, day and burst rate limits
Common questions
Can I restrict which fields an external system can write?
Yes. Each configuration has an allow-list of fields, and only those are accepted. The external system must use the exact field names you select.
How is the endpoint protected from abuse?
Requests are measured against rules you define — per minute, hour and day, with burst limits and block durations. A dashboard shows requests, blocked and suspicious traffic, and you can whitelist IPs that should bypass the rules.
Can an API call trigger automation?
Yes. A common pattern is external app → WebToCRM endpoint → custom object record → Flow trigger, which lets an outside event drive a full workflow inside Alano.