Speed of Glide API when making multiple subsequent requests to add new row

Ask for Help
1

I have an leads generation/Business development application ive developed which includes a component of contact prospecting. The functionality essentially recognises when a company’s profile screen is selected and at that moment, it searches for LinkedIn profiles on google search (using a custom google search engine API), modifies the URL title to obtain the persons name, job title and company name, and then uses some logic to generate and validate an email address for them, based on a series of permutations of their name and the companys email domain.

The problem im having is that:

  1. The logic is too complicated (for me anyway) to accomplish in glide alone
  2. By executing the logic outside glide, i then have to wait for the glide API to add in each prospect one by one, which is excrutiatingly slow when a series of say 20-30 prospects are identified for a company

Can anyone suggest or identify an alternative method that i can implement this. Ive tried so many things, but ultimately keep finding the rate limiting step is the glide APIs speed capability when adding multiple rows. (NB: it may be the rate at which im sending requests to the glide API but I didnt believe this was the case as I have tried alternatives which appeared much quicker).

1 Like
2

Question: are you adding the rows one by one as separate API calls, or all at once with a single call? The latter would generally be much quicker.

1 Like
3

At the moment im adding them one by one because for some reason I was under the impression that separate rows needed to be added this way using the Glide API. Can you add multiple separate rows via a single API call? Im not sure i know how to do this, if it is possible.

4

Yes, you can. You can add as many as 500 in a single call. You can even mix adds/edits/deletes in the same API call.

Each API call should contain an array of mutations. Sounds like you are sending an array of one. A call to add two rows would look something like the following:

{
  "appID": "xxxxx",
  "mutations": [
    {
      "kind": "add-row-to-table",
      "tableName": "native-table-xxx",
      "columnValues": {
        "Name": "Name 1",
        "Image": "Image 1"
      }
    },
    {
      "kind": "add-row-to-table",
      "tableName": "native-table-xxx",
      "columnValues": {
        "Name": "Name 2",
        "Image": "Image 2"
      }
    }
  ]
}
3 Likes
5

im currently using a Make.com scenario that looks like this…

image
image2811×1441 161 KB

Would this simply be fixed by adding an aggregator after the Create JSON module and before the HTTP module, or is it more complicated than this?

6

More or less, yes.
But assuming that your JSON module is currently creating the entire data payload, you would need to adjust that so that it only creates the mutations. Then you’d need a second JSON module after the aggregator that wraps the mutations up with the AppID.

2 Likes
7

Hrmmm so a bit more complicated. Hopefully i can figure that out by myself then.

Thank you so much for your help. I wish i’d asked sooner, as you’d have saved me days of work. If i could like your posts more than once, i would!

2 Likes
8

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