Import CSV Contacts to Notion Database
Pulls a contacts CSV from Google Drive and maps the data into your Notion database.
founders and execsops and IT teams
What it does
Import your contacts from Google Drive directly into Notion by mapping names, emails, phones, and companies to your database instantly. This workflow pulls the CSV file you select and populates your records without manual entry.
Step by step
- Set up the Google Drive trigger to watch for new CSV files in a specific folder
- Define the target Notion database schema with properties matching name, email, phone, and company
- Map the extracted CSV columns directly to the corresponding Notion property IDs using standard string parsing
Where the LLM does the work
- Generate robust error handling logic for malformed CSV rows that lack required fields like email addresses
- Write the data transformation script to normalize inconsistent date formats or phone number structures found in real-world exports
- Create a deduplication check mechanism to prevent duplicate entries when importing contacts that may already exist in Notion
Watch out for
CSV files often contain hidden whitespace or special characters, so trim all string values before sending them to the database.
Email validation is critical because Notion will reject invalid email formats, so add a regex check to filter out bad addresses.
The Google Drive trigger may fire on file edits rather than just new uploads, so configure it to only watch for newly created files.
Tools that fit
Code API Data transformation and mapping
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Import CSV Contacts to Notion Database: Pulls a contacts CSV from Google Drive and maps the data into your Notion database. ## Specification - What it does: Import your contacts from Google Drive directly into Notion by mapping names, emails, phones, and companies to your database instantly. This workflow pulls the CSV file you select and populates your records without manual entry. - Trigger: Run manually (Manual · on demand) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - Google Drive: Source CSV file storage - Notion: Destination database for contacts - Code: Data transformation and mapping ## Known pitfalls, handle each one explicitly in your implementation 1. CSV files often contain hidden whitespace or special characters, so trim all string values before sending them to the database. 2. Email validation is critical because Notion will reject invalid email formats, so add a regex check to filter out bad addresses. 3. The Google Drive trigger may fire on file edits rather than just new uploads, so configure it to only watch for newly created files. ## Reference implementation https://n8n.io/workflows/5612 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/import-csv-contacts-to-notion-database/ via usecasesforagents.com
Frequently asked questions
Can I use a different Cloud Storage than Google Drive?
Yes. Google Drive is only the example cloud storage in this recipe. The same flow works with Dropbox, Google Cloud Storage, Microsoft OneDrive and Nextcloud. Swap the cloud storage connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for founders and execs who need personal productivity handled without hiring for it.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.