Auto-Populate Request: CRM Record Lookup During Import

Andreas W. · 2025-03-27 17:26:10.893749+00

hey hey, *Auto-populate* request: *Lookup Record* when importing from a CRM

Auto-Populate Request: CRM Record Lookup During Import | Clay

11 comments

· Sorted by Oldest

Channeled
APP
·
·
When importing from a CRM, you can use the "Lookup Object" action to auto-populate and lookup records. Here's how: 1. Select your CRM account (e.g., Microsoft Dynamics 365). 2. Specify the "Object Type" you want to lookup. 3. Define at least one field to filter by and provide corresponding filter values. 4. Optionally, specify which fields to return (if none selected, all available fields will be returned). 5. Configure run settings, including auto-update for new rows. For other CRMs like HubSpot, the process is similar: 1. Use the "Actions" dropdown and select "Import". 2. Choose your CRM (e.g., "Import Contacts from HubSpot"). 3. Authenticate your account and select the list to import. 4. Optionally, customize data preferences. 5. After import, you can extract specific data points to separate columns for better organization. This process allows you to efficiently lookup and auto-populate records when importing from your CRM.
Sources: Import from CRM [Clay 101] - Clay University Microsoft Dynamics 365 CRM integration overview | Documentation | Clay University
Channeled
APP
·
·
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Bruno R.
·
·
Hi Andreas, thanks for your message - just to clarify, your request concerns running an object lookup to retrieve all fields associated with a specific object by default, when setting up a new CRM source?
Andreas W.
·
·
correct Bruno!
Andreas W.
·
·
I don’t see a use case where I don’t need that data when pulling an object.
Bruno R.
·
·
Got it, thank you Andreas - relaying this to our engineering team!
Andreas W.
·
·
maybe I’m just overlooking a simple way, so maybe it’s not an engineering issue but UX wise it’s a high lift to get this flowing into the CRM
Bruno R.
·
·
Using the lookup action would be the way to go for now, but I think the point of pulling in all fields by default makes sense here!
Andreas W.
·
·
Oh - this was the wrong thread
Channeled
APP
·
·

Channeled
APP
·
·
When importing from a CRM, you can use the "Lookup Object" action to auto-populate and lookup records. Here's how: 1. Select your CRM account (e.g., Microsoft Dynamics 365). 2. Specify the "Object Type" you want to lookup. 3. Define at least one field to filter by and provide corresponding filter values. 4. Optionally, specify which fields to return (if none selected, all available fields will be returned). 5. Configure run settings, including auto-update for new rows. For other CRMs like HubSpot, the process is similar: 1. Use the "Actions" dropdown and select "Import". 2. Choose your CRM (e.g., "Import Contacts from HubSpot"). 3. Authenticate your account and select the list to import. 4. Optionally, customize data preferences. 5. After import, you can extract specific data points to separate columns for better organization. This process allows you to efficiently lookup and auto-populate records when importing from your CRM.
Sources: Import from CRM [Clay 101] - Clay University Microsoft Dynamics 365 CRM integration overview | Documentation | Clay University
Channeled
APP
·
·
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Bruno R.
·
·
Hi Andreas, thanks for your message - just to clarify, your request concerns running an object lookup to retrieve all fields associated with a specific object by default, when setting up a new CRM source?
Andreas W.
·
·
correct Bruno!
Andreas W.
·
·
I don’t see a use case where I don’t need that data when pulling an object.
Bruno R.
·
·
Got it, thank you Andreas - relaying this to our engineering team!
Andreas W.
·
·
maybe I’m just overlooking a simple way, so maybe it’s not an engineering issue but UX wise it’s a high lift to get this flowing into the CRM
Bruno R.
·
·
Using the lookup action would be the way to go for now, but I think the point of pulling in all fields by default makes sense here!
Andreas W.
·
·
Oh - this was the wrong thread
Channeled
APP
·
·