Your CRM can send leads straight into Sustentus

Until now a lead reached the platform one way: somebody typed it in, or pasted a spreadsheet into the importer. If you run your pipeline in a CRM, that meant entering every opportunity twice.

There is now an inbound webhook. An external system posts the lead — the customer’s contact details, the product and service, a description — and Sustentus creates it. The result is not a lesser kind of lead: it gets the same request number, the same starting status, the same activity trail and the same journey as one raised by hand. A customer who is new to you is set up exactly as they would be if you had entered the lead yourself.

Setting it up

Open Admin → Settings → Integrations. The inbound lead webhook card shows the address to post to and lets you generate a key.

The key is shown once, when you generate it. Copy it then — it cannot be shown again, because we do not keep a copy. If it is ever lost or exposed, revoke it and generate another.

You can hold two keys at once, which is there so a changeover is not a cliff: generate the new key, switch your CRM across, then revoke the old one once you are sure nothing is still using it.

Seeing what arrived

The same card lists recent deliveries. Each one says what happened — accepted, a duplicate, or rejected — and, when something was rejected, why. A wrong key reads differently from a wrong payload, so you can tell which end to fix without asking anyone to read server logs. Deliveries stay on the list for 30 days.

A note for whoever builds the integration

Have it send its own id for the deal alongside the lead. If it does, a repeat of the same delivery is recognised and ignored rather than creating a second lead — which is what makes it safe for your system to retry after a timeout. The full reference, including the exact payload and what each response means, is in the technical documentation.