One webhook for everything
Not every tool has its own integration. Your own webhook accepts deliveries from any system that can send webhooks. You see what arrives in TSO, with everything read from it.
More on the API & webhooks page.
Any tool that can send a webhook sends leads, deals and payments to TSO. Email, phone and name are detected automatically; you map everything else.
| Field | Meaning |
|---|---|
| Email, phone, name | Detected automatically through the usual field names. |
| Value and currency | For revenue from deals and payments. |
| ID of the person and the submission | External ID, so repeats don't count twice. |
| Visitor ID | lt_visitor_id, to attribute a submission to exactly one visit. |
| Other fields | As answers or lead attributes on the lead. |
Not every tool has its own integration. Your own webhook accepts deliveries from any system that can send webhooks. You see what arrives in TSO, with everything read from it.
More on the API & webhooks page.
| Problem | Solution |
|---|---|
| "No email and no phone found." | Name the fields email and phone or map them. |
| Deliveries were read wrong. | Fix the mapping and reprocess earlier deliveries; nothing counts twice. |
| Nothing arrives. | Check that the URL is right and the integration is switched on. |
Any that can send a webhook, such as CRMs, booking tools, form tools, Zapier or Make.
Yes. Per webhook you choose which event a delivery counts as, and map value and currency.