dotLoop and darwin Cloud's API engine have made it possible to pull loop data from dotLoop into darwin Cloud to create new transactions and listings. Also additional information can be added to listings and transactions that were pulled from the MLS, other sources or even manually entered.
These steps need to be completed with a dotLoop user that has access to all the offices you want darwin to pull loop information from.
It is best if this is done on a call with the integrations team as the generated code is only valid for a short time.
click approve
Your bowser will redirect to the AccountTECH website. Provide the AccountTECH Integration Team the code at the end of the URL.
With this code the AccountTECH team will be able to proceed with your Dotloop integration setup.
The dotLoop information is typically used to augment the data we get from other sources like the MLS. By default if we get pending date from both the MLS and dotLoop, we trust the MLS data over the dotLoop data when updating property information.
darwin Cloud matches the property from dotLoop to the property in darwin Cloud by the MLS #. This means that you need to make the MLS # field in dotLoop mandatory and train your agents to give non-MLS listings a unique MLS # (ex. Fsbo-123 Main Street). If dotLoop is your only source of property data then we will match on Loop ID.
We have set up 3 default dotLoop templates that can be imported and modified to fit your needs.
If you are only pulling from dotLoop and not from any other MLS feeds, then
If you need to pull a record from dotLoop on demand, you will need to get the Loop View ID from dotLoop. This is different from the Loop ID on the details page.
The number you need is in the URL of the Loop and not the Loop ID under the address.
If you use the Loop ID you will get this error:
Here is the list of the dotLoop Fields that are mapped to darwin Cloud fields and the default update rules.
| dotLoop Field | darwin Cloud Field | update Rule |
| Address City | city | IF NULL |
| Address MLS Number | mlsNumber1 | IF NULL |
| Address State | state | IF NULL |
| Address Street Name | streetName | IF NULL |
| Address Street Number | streetNumber | IF NULL |
| Admin Company Name | companyID | IF NULL |
| Appraiser | propertyPeople | ALWAYS |
| Bathrooms | FullBaths | IF NULL |
| Bedrooms | bedrooms | IF NULL |
| Buyer 2 Last Name | propertyPeople | ALWAYS |
| Buyer Attorney Contact | propertyPeople | ALWAYS |
| Buyer Last Name | propertyPeople | ALWAYS |
| Buying Agent Contact | Buyer Agent | ALWAYS |
| Closing Date | estimatedClosingDate | IF NULL |
| Contract Date | pendingDate | IF NULL |
| Escrow Title Contact | propertyPeople | ALWAYS |
| Home Inspector Contact | propertyPeople | ALWAYS |
| Lender Contact | propertyPeople | ALWAYS |
| Listing Agent Contact | List Agent | ALWAYS |
| Listing Date | listDate | IF NULL |
| Listing Expire Datae | expiredDate | ALWAYS |
| Loan Processor | propertyPeople | ALWAYS |
| Loop ID | dotLoopID | ALWAYS |
| Loop Status | Status | IF NULL |
| Lot Size | lotSize | IF NULL |
| Lot Size | lotSizeUnitID | IF NULL |
| Original List Price | listingPrice | IF NULL |
| Postal Code | zip | IF NULL |
| Property Type | accounting classification | IF NULL |
| Property Type | propertyType | IF NULL |
| Property Type | transactionType | IF NULL |
| Property Type | typeCode | IF NULL |
| Purchase Price | sellingPrice | IF NULL |
| Seller 2 Last Name | propertyPeople | ALWAYS |
| Seller Attorney Contact | propertyPeople | ALWAYS |
| Seller Last Name | propertyPeople | ALWAYS |
| Square Feet | squareFeet | IF NULL |
| Square Feet | squareFeetUnitID | IF NULL |
| Year Built | yearBuilt | IF NULL |
We typically do not see clients using these loop transaction types but they can be set up if needed.
We get many questions about what HAS to be filled in for a dotLoop record to pull on schedule successfully.