In a race against the clock to generate a dynamic template item from a form submission, I'm wondering which of these Zapier actions would be better for speed

  1.  Webflow Form Submission —> Find in Airtable —> Create Airtable Record —> Create Live Item in Webflow  ...or...
  2. Webflow Form Submission —> Find in Airtable — Create Live Item in Webflow —> Create Airtable Record

In other words, is it faster to have two Airtable actions in a row? Does that reduce latency at all? Or is that not how that works?

Upon Webflow Form Submission, the page is redirected to the user's dashboard, where they should see a new template item on their screen.

A little stuck on this one—hope everyone had an awesome Thanksgiving (for those who celebrated :)
In my experience, I don't think the order of actions affects latency as much. In this case I'd lean Airtable → Airtable → Webflow to keep things easier to understand/debug in case someone else were to jump in to use it. 🙂
Hey, Naitik! Hmm yeah, that's definitely something to consider as well..
I'd agree with Naitik. 

The biggest slow down will typically be when you hop from one service to another. That produces network latency, e.g. it takes time to travel across the network from one server to another. 

If, for example, you were using Integromat as your backend and swapped out Airtable for the Integromat Datastore, you'd have a higher likelihood of significant speed improvements. 

The actions you are performing would most likely be within the same network - physically close to each other, or travel across a private, high speed backbone with very low latency.
Thanks for the second opinion, Chris.
So basically, the summary is that it's better to handle tasks within one platform, and then switch to another platform, versus hopping between platforms back and forth.

Thanks for this guys. These tiny speed increases can make a big difference!

Post a comment

Log in