Leads from a form or app
Give an automation its own web address so your website form, Zapier, Make or IndiaMART can post enquiries as leads.
Updated 8 Oct 2026
Enquiries arrive from many places: your website's contact form, IndiaMART, a landing page. Instead of copying each one in by hand, point the form at KretaOS. Every enquiry becomes a lead, with the message on its timeline, and the automation takes it from there.
Set it up
- On Automations, create an automation (start from Blank).
- Click the trigger card and choose A form or app sends a lead.
- Add the steps you want, for example Assign owner to share the lead and Create task to call them. Press Save.
- Press Create address. KretaOS shows your webhook address once: copy it now, it won't be shown again.
- Paste the address into your form tool, Zapier, Make or IndiaMART bridge as the place to send new leads.
- Switch the automation on.
Lost the address? Press Make a new address. The old one stops working at once.
What to send
Send a POST with a JSON body. It needs a name or company, plus an email or phone number:
{"name":"Ravi","company":"Northwind","email":"ravi@northwind.example","message":"Need a quote"}Common field names from form tools and IndiaMART are understood too, such as full_name, mobile, company_name or enquiry. A source field, if you send one, is kept with the lead.
What happens to each enquiry
- Already in your book? KretaOS matches the person by email or phone and adds the enquiry to their page.
- New? A new lead is created with the email or number they gave. You can message them there; if they ask you to stop, record the opt-out on their page.
- Their message is logged on the timeline, shared with the team, and read for facts like any other touch.
- The automation runs for that lead. A new lead also counts for A new record is added triggers.
Good to know
- The address works only while the automation is on. A paused automation refuses enquiries, so your form tool can show an error.
- Keep the address private. Anyone who has it can create leads. If it leaks, make a new one.
- Send one enquiry per request. Requests are limited in size and in how many can arrive per minute, which is far above what a real form sends.
Web request: sending data out
The opposite direction is the Web request step: it sends the client's details to another app, such as a Zapier hook, with a body you write using variables like {{client.name}}. Only secure (https) addresses are allowed, and it is admin-only because it sends client data outside KretaOS.
Related
- Triggers — The trigger is the "when" of an automation. Here is every trigger KretaOS offers and when each one fires.
- Share new leads in turn — Use the Assign owner step to hand each new client or lead to the next teammate in turn, so enquiries are shared fairly and nobody is missed.
- Steps — What each automation step does — wait, check a condition, draft with AI, send, create a task, notify, fill fields and more.
- Consent and the DPDP Act — A dated consent record per contact and channel: opt-outs are always honoured, and a recorded yes can be required.
Or write to contact@tamkis.com