A booking system, a cash register, a loyalty app, a homemade customer list — if your developer can make it tell Hamla when something happens, Hamla can market on it. This page is written for them; show it to whoever handles your tech.

Early access — working today, still improving
Using something we don't support yet? Your developer can connect it.
A booking system, a cash register, a loyalty app, a homemade customer list — if your developer can make it tell Hamla when something happens, Hamla can market on it. This page is written for them; show it to whoever handles your tech.
🔒 Your tools send updates to Hamla — we never reach into your systems.
What you get
POST JSON to a Hamla webhook endpoint — a contact identifier, an event name, and any fields you want usable in messages. You define the schema.
Send a timestamp with each event and you can backfill years of history without triggering campaigns on old activity.
Once your developer sets it up, you use it like Salla or Calendly — pick the moments, approve the messages, watch it run.
How it works
- Create a webhook endpoint in Hamla — it gives you the URL and the expected shape.
- Your system POSTs events to it as they happen.
- Each event becomes a moment the owner can attach campaigns to — no more code involved.
Related integrations
Custom API integration questions
I'm not technical — is this page for me?
It's for your developer — that's deliberate, and it's the only page on this site written for them. What they set up once, you use without touching code.
What does the payload need?
JSON with a contact identifier, an event name, and whatever fields you want available in messages. Everything else is yours to define.
Two minutes to connect. Working by tonight.
Connect Custom API to your Hamla account and start automating your campaigns.
Free plan · no credit card needed


