Quick guide
The EZA integration enables the automatic import of leads from the "Einfach zum Angebot" portal. After a one-time setup, new leads are retrieved automatically, assigned to your system and made available for further processing.
Detailed setup
Requirements
- Active account with Einfach-zum-Angebot.de
- Valid API token from your EZA portal
- At least one lead type created in Leadnodes
Step-by-step guide
- Create the integration: Navigate to Integrations → New integration and select "EZA - Einfach zum Angebot".
- Enter the API token: Enter your API token from the EZA portal. The token is stored in encrypted form.
- Test the connection: Click "Test connection" to check that the EZA API is reachable.
- Lead type mapping: Map the EZA lead types to your internal lead types. At least one mapping is required.
- Configure field mapping: Optionally adjust the mapping between EZA fields and your lead fields.
- Activate the integration: Save the settings and activate the automatic import.
Test import
After setup, you can use "Test fetch" to check which unprocessed leads are available in the EZA system. You can import individual leads manually as a test before activating the automatic import.
Further frequently asked questions
What happens if a lead has already been imported?
The integration detects duplicates based on the external lead ID. Leads that have already been imported are skipped and not created again.
How is the lead data mapped?
Standard fields such as name, email, phone and address are mapped automatically. You can assign additional EZA fields to individual custom data fields via the field mapping.
What does the status "unprocessed" mean in EZA?
EZA marks successfully imported leads as "processed". This way, only new leads are retrieved on the next import. During a test import, leads are not marked as processed.
Can I adjust the import schedule?
Yes. After activating the integration, you can configure the import schedule (routine) under the advanced settings.
What happens if the lead type mapping is incorrect?
Leads without a valid lead type mapping are not imported. You receive an error message naming the affected EZA lead type. In this case, add the missing mapping in the integration settings.