API issues / speed issues?

Suggestion Box
1

This is kind of a piggy-back off my other post about slow coda automation speed.

I’m having a lot of trouble getting automation tools like Make.com or Pabbly to make successful api calls to Coda.

At first I was having issues mapping fields in the “Update Row” module in make and thought it was a make problem. But I also get the same problem in Pabbly. Also, the problem seems to be intermittent on both platforms (sometimes it works, sometimes it doesn’t), which makes me think it’s a problem with coda api.

Also I notice that when the api mapping calls aren’t working for these tools, the automation speed seems to be very slow at the same time.

There is an automation that I was running yesterday which was firing in a couple of seconds and is now taking 30-50 seconds, so I think these things might be related.

Anyone else noticing this?
Is there some kind of congestion issue with the coda api / automation? If so, is this common?

I was really set on creating this MVP project on coda, but these api issues could be a deal breaker. It would be great if we could just pay a higher tier for faster api speeds, but I wonder if that’s even technically possible.

2

Hey @Peter_Griffin ! Thanks for reaching out. After passing this along to our team, they noted that it looks like the API does work, but the responses are not as fast as you’d like them to be. That said, we have moved this post into the Suggestion Box for other members of the Community to chime in on this. We’ve gone ahead and tracked your vote for the “ability to increase/pay/upgrade for a faster API response” feature formally.

3

great idea, thank you!