Zap Email Parser

To request trial, please follow the below steps:

Step 1: Request solution file: Email support@zapobjects.com to request solution file.
Please mention:
– Company Name:
– Contact Phone:
– Need Demo: Yes / No
– Requirements in brief:
You can expect a response within 1-business day. Please use only official email address for communication.

Step 2: Import the solution file.

Step 3: Activation of 15-day trial:
Browse to Settings >> Zap Apps and open Zap License. Register the profile online, to start 15-day trial. (Refer Licensing KB articles for more info)

Feel free to email support@zapobjects.com if you have any questions.

Some areas of user-guide are password protected. Email support@zapobjects.com from your official email address to request password.

Solution Version: 27.0.1.9 [Latest]
Works with: PowerApps, Dynamics 365  v9
Dynamics 365 Supported Versions: This version supports Dynamics 365 v9 and is compatible with Unified Interface forms.
Works for Online as well as On-Premise.
Release Date: Apr 02, 2022
Updates:
1. Ability to configure Email Alias
2. Please note that there is a new field called as “Queue Email Address” added to configuration..
For existing parsing configuration… this field needs to be manually populated…(for new configurations… we will automatically populate this field)

Solution Version: 25.1.1.9
Works with: PowerApps, Dynamics 365  v9
Dynamics 365 Supported Versions: This version supports Dynamics 365 v9 and is compatible with Unified Interface forms.
Works for Online as well as On-Premise.
Release Date: Aug 18, 2021
Updates:
1. Major changes in code to optimize the executions.
2. Ability to define a configuration as default configuration. So if none of the filter conditions match then you can have this default configuration executed. For more details, refer link
3. Ability to build multiple parsing rules for same field… such that only the rule that returns a value is updated in the field.
Example Scenario: You are trying to extract value for field “Preferred_Phone” from email body.
However the matching text for phone number is different across your emails. Some examples of possible matching text are: “Phone number:”, “Phone:”, “Telephone Number:”, “Telephone:”
Now you can create multiple parsing rules for the same field (“Preffered_Phone”)… and only the rule that returns a value will be used to set this field!

Solution Version: 20.4.1.9
Works with: PowerApps, Dynamics 365  v9
Dynamics 365 Supported Versions: This version supports Dynamics 365 v9 and is compatible with Unified Interface forms.
Works for Online as well as On-Premise.
Release Date: Jul 01, 2020
Updates: Compatible with Power Apps

Solution Version: 10.0.1.8 (built for 2016 / Dynamics 365 v8)
Dynamics Supported Versions: This version supports CRM 2016 as well as Dynamics 365 (However Unified Interface Forms are not supported). Works for Online as well as On-Premise.
Release Date: Dec 01, 2019