Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

The id of the account to update.

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

The id of the lead to update.

Note: The Zap Editor does not currently support Lookup fields during search

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

The ID of the email verification job to delete.

An input file containing the email addresses to verify.

By default, we use the MIME type returned with the file.

Advanced: the zero-based number of the first row to import and process; if not specified, we start from the first (0) row.

Advanced: the zero-based number of the last row to import and process; if not specified, we process rows until the end of the file.

Advanced: valid only for Plain Text and Delimiter-Separated Values files. By default, we attempt to guess the correct line ending.

Advanced: valid only for Delimiter-Separated Values files. By default, we use the comma symbol (,).

Advanced: valid only for Delimiter-Separated Values and Excel files. The zero-based index of the column to import. If not specified, we use the first (0) column.

Advanced: valid only for Excel files. The zero-based index of the worksheet to import. If not specified, we use the first (0) worksheet.

The higher the quality level the longer it could take to complete the verification. By default, we use the configured default quality level for your Verifalia user.

Choose whether / how we should mark duplicated email addresses.

The retention period to observe for the validation job, expressed in the format dd.hh:mm:ss (where dd: days, hh: hours, mm: minutes, ss: seconds); the initial dd. part is added only for periods of more than 24 hours. The value has a minimum of 5 minutes (0:5:0) and a maximum of 30 days (30.0:0:0): Verifalia will delete the job and its data once its data retention period is over, starting to count when it gets completed.

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

The id of the contact to update.

API docs for Microsoft Dynamics 365 CRM are located here https://docs.microsoft.com/en-us/dynamics365/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

Note: The Zap Editor does not currently support Lookup fields during search

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

Note: There may be some fields missing because the Zap Editor does not currently support image fields nor unique identifier fields.

The higher the quality level the longer it could take to complete the verification. By default, we use the configured default quality level for your Verifalia user.

The retention period to observe for the validation job, expressed in the format dd.hh:mm:ss (where dd: days, hh: hours, mm: minutes, ss: seconds); the initial dd. part is added only for periods of more than 24 hours. The value has a minimum of 5 minutes (0:5:0) and a maximum of 30 days (30.0:0:0): Verifalia will delete the job and its data once its data retention period is over, starting to count when it gets completed.

No setup is required for this action.