Vertify Help Center

DynamicsREST Connector: Setup + FAQs

What is it?

  • Vertify's DynamicsREST connector can be used to connect with the endpoint system directly for the integration.

Where do I begin?


This setup guide will require the system administrator to complete steps outlined below in order to connect the external system application with Vertify.

Please note, this document may be subject to change and additional information required. Partnership with system administrator and/or support team may be necessary.

This connector uses the OAuth process to authenticate the API connection to Dynamics.


Register a new Dynamics 365 App. You will create a unique App ID with specific rights to access your Dynamics instance.

  1. Connect to the Microsoft Entra ID (Azure Portal) with administrator credentials.
  2. From the homepage, click on Identity -> Applications -> App registrations
  3. Click New registration
  4. Name: Enter a meaningful name, e.g. Vertify Integration
  5. Supported Account Types: Select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)
  6. Set the Redirect URI. Choose Web and enter
  7. Click Register
  8. Note the Application (client) ID value. This is the Client Id connector parameter and will be needed in Vertify.
  9. Next click API Permissions and click Add a permission
  10. Select Dynamics CRM, check the box user_impersonation and click Add permissions
  11. Click Certificates and Secrets, then under Client Secrets click New client secret
  12. Description: Enter descriptive text for example Vertify Integration
  13. Expires: choose an expiration date e.g. 24 months
    1. Note that you will need to refresh the secret when it expires and update the secret at Vertify Connection Edit
  14. Click Add
  15. Note the secret value. Client secret values cannot be viewed, except for immediately after creation. Be sure to save the secret before leaving the page. This will also be needed in Vertify.
  16. Your app is now registered and ready to be used by Vertify to connect to Dynamics


  1. Navigate in Dynamics to Settings -> Customization -> Developer Resources
  2. Under Instance Web API note the Service Root URL e.g.
  3. Using that example, the connector parameters would be:


Custom fields are required to be created on the Lead and Contact Objects in Dynamics for the Vertify integration. 

Reference the API Name column in the table below for the list of how to title the fields, the needed data type, and the purpose of the field for context.

API Name Data Type Purpose
MAPContactId String This field will be used to house the marketing automation platform’s Contact’s internalId, and for merging and lookup purposes in Vertify.
MAPCompanyId String This field will be used to house the marketing automation platform’s Company’s internalId, and for merging and lookup purposes in Vertify.
SyncToMAP Boolean This field will be hard-coded by Vertify or by a workflow in Dynamics. It is used to determine which records are eligible to move back to the marketing automation platform and for filtering in Vertify.



  1. Navigate to your Vertify tenant site provided by your Customer Success Manager. 
    1. Reach out to them directly if you have any questions or need assistance.
    2. Follow the reset password link to pick a permanent password for your account.
  2. On the main Dashboard, click Workspaces.
  3. Click the Workspace link you want to create a system in.
  4. Click New System at the Vertify workspace Systems page
  5. Select Remote System DynamicsREST
  6. Enter the Client Id, Client Secret, Dynamics Instance Url and Dynamics Version values
  7. Click Save
  8. Click Connect With DynamicsREST
  9. After authenticating to Dynamics with an identity that has full access to Dynamics, click Save
  10. Click the Collect tab and click Rescan for the DynamicsREST connection

Please reach out to our support team for further assistance as needed, or your Vertify One Team.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.