Many business processes start outside your own CRM system: a form on a landing page, an event in another specialist system, a message from an external application. So that this data does not have to be entered by hand, 1Tool offers incoming webhooks – a way to receive external data automatically and in a structured form instead of transferring it manually.
A unique URL instead of complex authentication
In 1Tool you can create your own webhook endpoints. Each of these endpoints receives a unique, publicly reachable URL. External systems can send data to this URL – for example when a certain event occurs there – without having to authenticate separately first. The security of this mechanism rests on keeping the unique URL itself secret. In practice, this approach is sufficient for many integration scenarios, since the URL cannot be guessed or reused without knowing it, and at the same time it makes connecting the external system as simple as it gets: no credentials, no token exchange, no additional authentication logic.
Complete logging and flexible field mapping
Every incoming call is first logged in full – including headers and the content actually transmitted – before it is processed at all. This lets you trace afterwards exactly what an external system really sent, which is especially valuable for troubleshooting while setting up a new integration. One of the supported processing types is generic contact creation: any incoming JSON fields can be mapped directly to contact fields and custom fields in 1Tool via a configurable field mapping. Simple automatic type detection helps on top of that, so that numbers, text or date values, for example, are interpreted sensibly. In practice this means that an external system does not have to adapt its data format to 1Tool – which incoming field flows into which 1Tool field is configured on the 1Tool side.
Errors are not lost
If processing an incoming call fails – for instance because an expected field is missing or a value does not match the configured target type – the error is stored. A dedicated retry function then lets you trigger processing again without losing the original data. Especially for integrations with systems outside your own control, this is indispensable in practice: format changes on the sender's side or short-term configuration errors do not cause data to be lost permanently, but merely mean that a call can be reprocessed once the problem has been fixed. For companies that want to connect several external systems to their CRM, the difference compared to a rigid interface programmed individually for each system is considerable: instead of writing new code for every new data source, you simply configure a new field mapping.
Frequently asked questions
Does an external system have to authenticate with a 1Tool webhook?
No, security is based on keeping the unique, public webhook URL secret, so no additional authentication is required.
What happens if an incoming call cannot be processed correctly?
The error is stored and the call is retained. A dedicated retry function lets you trigger processing again later without losing any data.
Can I map any incoming fields to my own custom fields in 1Tool?
Yes, a configurable field mapping lets you map any JSON fields to standard and custom contact fields, supported by simple automatic type detection.
Which external data sources could you feed into your CRM automatically and in a structured way in future?
Read more
- Database per tenant: how 1Tool really solves multi-tenancy
- The 1Tool API: more than 2,500 endpoints, documented live