Webhooks & Event Subscriptions

Use this guide when you want KlickTipp to send contact data or deletion-request events to an external system.

Webhooks are useful when another tool must react to changes in KlickTipp without polling the API. Common targets include CRMs, databases, Zapier, Kajabi, Make, n8n, spreadsheets, data warehouses, and internal backends.

A KlickTipp webhook sends data to a configured URL when a specific event happens.

Typical webhook use cases include:

• sending contact data to an external system after a tag is applied
• forwarding contact data from KlickTipp to a CRM or database
• triggering automations in Zapier, Make, n8n, or Kajabi
• notifying another system after a campaign action
• forwarding deletion requests from the Privacy Dashboard
• documenting or processing data deletion in third-party systems

In older KlickTipp materials, this feature may be called Outbound. In the current KlickTipp interface, it is configured under Automation > Webhook.

Use webhooks when an external system must be notified automatically by KlickTipp.

Use an API call instead when the external system needs to actively read, search, create, or update data in KlickTipp.

Webhooks and APIs are often used together. A webhook can notify your integration that something changed, and your backend can then use the API for follow-up actions.

Use a secure HTTPS endpoint that receives the webhook and processes it asynchronously.

Recommended flow:

1. KlickTipp sends the webhook to your endpoint.
2. Your endpoint validates the request and payload.
3. Your endpoint stores the event or queues a background job.
4. Your integration processes the event.
5. Your integration logs the result and handles retries or manual review if needed.

Avoid putting complex business logic directly into the HTTP request lifecycle. Webhooks should respond quickly and process long-running work in the background.

1. Go to Automation > Webhook > New Webhook.
2. Enter a clear webhook name.
3. Optionally add a label.
4. Select the HTTP method: POST or GET.
5. For POST, select the payload format: Form Data or JSON.
6. Enter the target URL that should receive the webhook.
7. Select which contact fields should be sent.
8. Add static values if the receiving system requires fixed parameters.
9. Save and test the webhook.

Contact data webhooks can be triggered by manual tags, SmartTags, SmartLinks, or campaign actions.

1. Go to Automation > Webhook > New Webhook.
2. Enter a clear name for the deletion webhook.
3. Choose a manual tag for the webhook.
4. Paste the activation URL from the third-party provider or your own endpoint.
5. Create the webhook.
6. Go to Tools > Privacy Dashboard.
7. Open Settings.
8. Select the webhook that should run for deletion requests.
9. Test and document the complete deletion workflow.

Deletion webhooks help trigger follow-up deletion work in connected systems after KlickTipp processes a deletion request.

Before creating a webhook, define which KlickTipp objects trigger or support the workflow.

Choose stable names so the webhook purpose is clear to support teams and future maintainers.

Only send data that the receiving system needs.

For POST webhooks, prefer JSON when the receiving system supports it. Use Form Data when the target tool expects form-encoded fields.

For supported field formats, see Data Field Types and Input Formats.

Choose the trigger based on the business event.

If a webhook is triggered by a tag, it can only run once every 6 hours for that tag-triggered flow. Webhooks triggered by campaign actions run immediately.

Webhook endpoints should be treated as production integration endpoints.

Recommended safeguards:

• use HTTPS endpoints only
• include a static secret or routing token when the receiving system supports it
• validate required fields before processing the event
• avoid sending unnecessary personal data
• store logs with appropriate retention rules
• restrict who can edit webhook URLs and static values
• document deletion workflows for data protection audits

For deletion requests, make sure the connected system actually deletes or marks the corresponding record according to your data protection process.

Test every webhook before using it in production.

Common issues include:

• target URL is not reachable
• target URL expects another HTTP method
• payload format does not match the receiving system
• required fields are missing
• static credentials or routing values are incorrect
• receiving system rejects duplicate events
• deletion workflow is not documented or tested

If the receiving system fails, the integration owner must know whether the event should be retried, stored for manual review, or ignored.

For general API error handling, see Error Handling and Validation.

Use these references when building webhook-based integrations:

Webhooks let KlickTipp notify external systems when relevant contact or deletion-request events happen.

Use contact data webhooks for real-time outbound contact updates. Use deletion webhooks when KlickTipp deletion requests must also trigger cleanup in connected systems.

Reliable webhook integrations use clear triggers, minimal payloads, secure target URLs, tested deletion workflows, and explicit error-handling rules.