Does Pipedream Support Per Row Execution of Workflow on Google Sheets and How to Set It Up?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi folks, does Pipedream support capability to read one row at a time from Google Sheet and execute the a series of events within for that Row?

Context

  1. Currently the Pipedream API support for Google Sheet — get_value_in_range — which reads the entire dataset into memory.
  2. In my case, I would have about 5k-10k rows in Google Sheet. With the data (all of it) loaded in memory, I would send each row of data to some API for further processing.
  3. To ensure efficiency of the code, I would use asyncio to asynchronously send API request (Running a for-loop is not an option due to timeout constraints by Pipedream).
  4. Given the large number of rows and subsequently large number of QPS, this caused rate limit issues on the API I am calling.
  5. One possible solution is to have a workflow that executes per google sheet row. However, I do not find that support for it currently.
  6. Make.com has similar features, and their execution runs at a per-row basis on Google sheet which is what I am looking for.
    What I tried
  7. I added exponential back-offs to my asychronous function call, however that led to timeouts on Pipedream.
    Question: Does Pipedream support per row execution of workflow on Google sheet? If so, how can I set it up?

Screenshot 2025-04-09 at 9.02.38 PM.png
Screenshot 2025-04-09 at 9.02.38 PM.png972×1314 157 KB

Screenshot 2025-04-09 at 9.05.53 PM.png
Screenshot 2025-04-09 at 9.05.53 PM.png912×1530 160 KB

2

Hey ,

One possible solution is to have a workflow that executes per google sheet row. However, I do not find that support for it currently.
Make.com has similar features, and their execution runs at a per-row basis on Google sheet which is what I am looking for.
Given that Pipedream has not yet having looping feature in a workflow (coming soon). One workaround is that:

  1. Create a new workflow with HTTP trigger to call the external API.
    a. You can update the concurrency settings of this workflow following your API timeout limit
  2. Modify your existing workflow to call the HTTP endpoint of the new workflow in step (1)