# Integrating Glide App with Pipedrive CRM via AI Transcriptions

**URL:** <https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207>\
**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:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [July 27, 2023, 5:18am UTC](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207/13 "2023-07-27T05:18:03Z")

</div>

> [@Eden](#):
>
> additionally, I wonder if there’s a javascript to create an array of sequential Index ID’s based on the current row rather than entering them manually…

See below, use the 2nd option

> [@How do I create an auto-incrementing row number with Glide Tables?](https://community.glideapps.com/t/how-do-i-create-an-auto-incrementing-row-number-with-glide-tables/39572):
>
> This is a question that comes up a lot, so creating this topic to use as a reference. Typically, there are two distinct use cases when it comes to auto-incrementing row numbers. Use Case 1: – We need to generate a Part Number, or an Order Number, or an Employee ID. Once the number is generated, it should never change, even if rows are deleted. – The general approach for this use case is to maintain a static counter, use it to craft a suitably formatted ID, and increment it by one every time…

> [@Eden](#):
>
> I wonder the JSONata column is any quicker than the Transform JSON (which is essentially [jq](https://jqlang.github.io/jq/)), which is already publicly released. I wonder what the the difference is in general.

I believe it is much faster. I generally avoid the JQ column, because I’ve found it has performance issues.

> [@Eden](#):
>
> the problem with using this field or Transform JSON is that there’s no option to outline variables as we could in javascript, so there’s no way to reference the index…

Yeah there is. There is a rich syntax available. Check the JSONata docs.

---

_[View the full topic](https://community.glideapps.com/t/integrating-glide-app-with-pipedrive-crm-via-ai-transcriptions/64207)._
