In this article, you will learn everything about the “e-Ident” workflow action and how to effectively configure and use it within a workflow. This action queries micro-geographical data from Global Group TDA Germany GmbH via the e-Ident API and stores the complete result as a JSON object in a target field configured by you.
Prerequisites
Please note that in order to use this data query, the e-Ident package must first be installed and the external service configured. You can find important information about this in the e-Ident Help Center article. Only after this step will the e-Ident workflow action be available to you.
Configuration of the e-Ident Action
The data query is performed via the workflow action type “Retrieve eIdent Data”, which you can select within your workflow configuration under Actions in the Select Action dropdown menu, see screenshot.
Mapping
After selecting the e-Ident action type, the required data fields for e-Ident must be mapped in the workflow by linking them to the corresponding fields from the DataEngine record:
- Postal code (required field)
- City (required field)
- Street (including house number, required field)
- First name
- Last name
- Email address
- Phone number
- Date of birth
In addition, a target field must be defined in which the JSON result returned by e-Ident is written.
Notes and Tips
- To ensure the workflow action runs smoothly, your workflow must be configured correctly. You can find guidance on configuring the e-Ident workflow in the e-Ident Help Center article.
- Also take a look at our Help Center article on the general setup of workflows.