How to Speed Up Data Updates in Coda Tables with Over 5,000 Rows Using Make Integration?

Hello, I am creating a CRM for my office, where I manage my clients’ information.

They convert on my website through TypeBot, leaving their name, email, phone number, and the problem they are facing.

To receive the information, I use TypeBot + Make + Coda.

When creating a scenario in Make, I first need to query a row in a Contact table, and then create the opportunity (deal). For this, I use the “List Row” module.

The problem is that when I query the row in the table that I recently inserted, it returns that it doesn’t exist; only after a few minutes does it appear.

Is there any way to speed up the update of the information inserted into the Coda table?

P.S.: My contact table has more than 5000 rows, and my opportunity table as well.

Without full insight in your doc it id kind of hard to suggest improvements, but what comes to mind first is to use a Coda automation to handle any follow up action. The automation does not trigger until a new row exists in Coda. It does not matter whether that takes 10 seconds or x minutes, once it triggers, the information (new row) is available.

Unfortunately there is no way to “speed up” this action – as stated by @Eric_Koleda in this topic: API delayed response - #23 by Eric_Koleda

You’ll see that you Coda module on Make returns a mutation id value, which you can further check to see if the request you sent to Coda is done or not – so no real time API here.

I would consider give a unique ID to each lead as it comes from your website and create a line on the Contact and Deal tables, with that ID. Then you could simply reference the contact on the deal table by it’s ID to create the relation between the two tables.

Another option you may want to consider is creating a webhook-triggered automation to perform the full set of Coda operations. The Make workflow can pass relevant information to the webhook in the POST body, and then the automation can read that information and perform a multi-stage process. Since all of the operations are happening at the same time it won’t run into the issues with the API staleness.

Unfortunately a webhook can’t return data back to Make at the end of the automation, so if you need to read some new data in Make then you’ll be stuck waiting unfortunately.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.