I spent hours setting up a workflow. An Airtable reader node triggers a custom node (searches an API for some data) and updates the table. Made it work. I realize I don’t need it to run on every change to the table. I’m fine with it running once a week. When I add a time trigger and turn off the Activate as flow trigger, the whole workflow breaks.
Before:
After
Im very confused. Can someone help explain what happened here? Ask Gumploop is a supremely infuriating experience
Hey @Karthik! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={your_run_id}&workbook_id={workbook_id}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
You can find your run history here: https://www.gumloop.com/history
Hey @Karthik! The issue here is with the type of input the node is expecting. From your second screenshot, I can see that your custom node is running in loop mode, which means it expects a List as input. However, the Airtable Reader node is passing a single value.
If you expand the Airtable Reader node, the number of records to fetch is likely set to 1. Once you increase that to fetch multiple records, it should work as expected.
Alternatively, if you only want to process a single record—e.g. the latest row—you can disable loop mode in the custom node and any connected nodes that rely on it.
Let me know if that clears things up! You can also read more about type mismatches here: Type Mismatch Errors - Gumloop
The overall logic of single versus list input makes perfect sense to me. I used to be a developer back in the day. What I don’t get it, the only difference between the top and bottom is that I turned on or off “Activate as flow trigger”. Nothing else.
If flow trigger is on, it assumes and works with list input. I want to turn it off (so it not running an update on each small change in the Airtable). I’d rather have a time trigger so it can run like a cron job. But removing the flow trigger to add a time trigger breaks the whole thing. If anything, I can have both triggers but not just a time trigger. Does that make sense?
Hey @Karthik - I recorded a quick Loom video to walk through everything.
Let me know if this makes sense and works for you.
Omg that’s super helpful! Thank you!
No problem! 
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
