Webhooks

Webhooks is the delivery log for events Tripletex sends *into* DealJourney — a customer updated, an invoice charged — so you can see whether they arrived and what was stored. It is not a place to paste a URL and push CRM events out.

Inbound (this page). Tripletex tells DealJourney when something changed, instead of waiting for the next poll. Setup is one button after Tripletex is connected; there is no endpoint of yours to configure. See Set up Tripletex webhooks and Watch inbound webhook deliveries.

Outbound (a workflow action). To POST from DealJourney to Slack, Zapier or a system we do not integrate with, add Send webhook on a workflow rule. POST JSON to an external URL (Slack, Zapier, etc.). That is a developer task: something on the other end has to receive the call.

Check the marketplace first. A supported integration handles authentication, retries and field mapping that a webhook leaves to whoever is receiving it.

Watch the log after anything changes on the Tripletex side. Webhooks fail quietly — a green success can still store nothing, and a disabled subscription stops arriving without anyone getting an email. The monitor is the only place that becomes visible.