This automation ensures that contact deletion requests in KlickTipp are consistently reflected in Salesforce.
When a contact deletion webhook is triggered in KlickTipp, the scenario checks whether the contact is linked to a Salesforce Record ID. If a Salesforce ID exists, the corresponding record (contact) is automatically deleted in Salesforce. If no Salesforce ID is available, the scenario does nothing.
This prevents outdated or orphaned CRM records, supports GDPR-compliant data handling, and keeps your marketing automation and Salesforce CRM perfectly aligned without manual effort.
The template is ideal for businesses that use KlickTipp for email marketing and automation while managing sales contacts in Salesforce, and want to maintain clean, synchronized contact data across both systems.
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Adds a new contact. If a contact with the same email already exists, it will be updated.
Completes or aborts a job.
Creates a new manual tag
Creates a new bulk data job.
Creates a new record in an object.
Deletes a contact
Deletes a tag and removes it from all contacts
Deletes a record.
Downloads an attachment or a document.
Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.
A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.
Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.
Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.