# Integrating Glide App with Pipedrive CRM via AI Transcriptions **URL:** \ **Category:** Ask for Help\ **Tags:** data-sync, api\ **Created:** [July 21, 2023, 4:12am UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207 "2023-07-21T04:12:22Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![Eden](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eden/32/18651_2.png) [@Eden](https://community.glideapps.com/u/Eden)\ **Post date:** [July 29, 2023, 5:16pm UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/22 "2023-07-29T17:16:45Z")
Ok, now that it all works beautifully, I wonder if we could go one step further… Can we create a virtual Index? so instead of creating 100 rows, just have a single row, with all the columns. And if I’m looking to fetch all rows, create a virtual index to sort of fetch specific rows as if they existed. might be feasible with Query, Relations, and Joined Lists- while remaining lightweight. @Robert_Petitto any thoughts? ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [July 29, 2023, 5:49pm UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/23 "2023-07-29T17:49:08Z")
With the right JSON structure, it’s possible for f you wanted to query data… you just wouldn’t be able to display the data as collections unless you created helper tables to parse out the data onto their own row ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [July 30, 2023, 12:39am UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/24 "2023-07-30T00:39:55Z")
It’s a lot of work to save rows though. Personally I wouldn’t do 100 columns (or possibly more if you need multiple pieces of info in a “row”). ---
**Author:** ![Eden](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eden/32/18651_2.png) [@Eden](https://community.glideapps.com/u/Eden)\ **Post date:** [July 30, 2023, 9:12am UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/25 "2023-07-30T09:12:14Z")
Hmm, I guess what I essentially need is the ability to list them within collections/list. So I guess what ended up building are helper tables- and they’re nice and clean, with each table- Customers, Projects etc getting their own table. I was just wondering if there’s a way to avoid that, trying to push needle and simplify… @ThinhDinh what do you mean by 100 of columns? ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [July 30, 2023, 10:26am UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/26 "2023-07-30T10:26:54Z")
> [@Eden](#): > > so instead of creating 100 rows, just have a single row, with all the columns. I was referring to this. I don’t like tables with a lot of columns 😅 I almost always create helper tables for use cases like this. ---
**Author:** ![Eden](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eden/32/18651_2.png) [@Eden](https://community.glideapps.com/u/Eden)\ **Post date:** [July 30, 2023, 4:24pm UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/27 "2023-07-30T16:24:24Z")
No no 😅 By all the columns I meant ‘fields’, Org ID, Org Street, Org Address etc (I hate having many columns, and always try to simplify). And i wanted to actually having to create many rows within those helper tables. Do you have a screenshot of the different column in your helper tables? Helper tables are essentially an an index, correct? ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [July 30, 2023, 11:24pm UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/28 "2023-07-30T23:24:17Z")
> [@Eden](#): > > Helper tables are essentially an an index, correct? Yes, that’s correct. I usually use it when I have a JSON structure with multiple items, or a comma-delimited list with multiple items. The helper table would include index for each row, and I use that index to access each item in the JSON/list. [Previous page](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207.md?page=1)