What is your goal?
Get a new user automatically added as a row in a Glide table via Make’s “Add Row” module, as part of a New User Signup scenario.
What is the problem & what have you tried?
This scenario ran successfully on June 14, 2026 (confirmed success: 8 seconds, 14 operations). I have not edited this specific module since then. Starting June 20, every run fails at the final Glide module with no changes made on my end. Upstream modules (Webhooks, Google Sheets - Search Rows, Iterator) all complete successfully in the same run — only the Glide - Add Row module fails.
The Table field in this module also fails to load any tables when interacting with it directly in the editor.
What I’ve already tried (all fail identically): refreshing the existing connection, reloading the page/restarting the browser, creating a brand-new connection with a freshly copied API key directly from Glide’s Integrations settings, and opening the Table dropdown to switch to a different table (e.g. “Users”) — the dropdown itself fails to load before any table names appear, on both old and new connections.
This rules out a stale token, a corrupted connection, or anything specific to one table. Has anyone seen this exact pattern — a previously-working Glide Add Row module suddenly failing with no local changes?
Error messages or input/output bundles
Run ID: c5032fd98372499c818795891…
Timestamp: June 20, 2026, 2:15:07 PM
Code: RuntimeError
Message: [object Object] (unserialized object, not a readable string — even in Advanced Log)
Screenshots (scenario flow, module settings, errors)
Hello @Daniel_Jenkins,
Welcome to the community!
Could you please share your workflow or add some screenshots how your scenario is built? Please also attach Glide’s module configuration and results with input bundles.
Please hide any confidential information like user data which you are adding.
To debug it you can duplicate Glide module and add record with hardcoded data e.g. no mapping.
Your error states that you are trying to pass collection/array as string which can not be processed correctly by module throwing error.
But without knowing what data it is exactly used we can not suggest any solution.
Have a nice day,
Michal
Hi Michal,
Thanks for the quick reply! Here’s the input bundle for the failing Glide - Add Row module (screenshot attached):
Bundle 1: (Collection) App: Sajh61fNOhJ2QA6Lb5WT Active: false User Email: [email protected] Artist ID: A005 Supporting: false Table: native-table-6cf814ef-f6a3-467e-9702-cecd4e88408e
All fields here are flat strings or booleans — no arrays, no nested objects, no collections within the bundle itself. So I don’t think this matches the “passing collection/array as string” theory, at least not from what’s visible in the input.
A couple more details that might help narrow it down:
- The error itself shows: Code: RuntimeError, Origin: Glide, Message: [object Object]
- This exact scenario (same module, same mapping, no edits) ran successfully on June 14, 2026, and started failing on June 20 with zero changes on my end in between.
- The Table field in this module also fails to load any tables when I try to interact with it directly in the editor — the dropdown won’t populate, on both my existing connection and a freshly created one.
Given the error originates from Glide rather than Make, and the table-loading issue in the editor, I’m wondering if this might be related to Glide’s REST API access being gated behind their Business/Enterprise plan tier (I’m currently on Glide’s Maker plan) rather than a data-shape issue in the Make module config. But I’m not certain, and very open to other theories if this doesn’t fit what you’re seeing.
Let me know if you need anything else from my end — happy to duplicate the module with hardcoded data as you suggested if that would help isolate it further.
Thanks again, Daniel
Hi Michal,
Quick follow-up with some useful context from further digging today.
First — a sharper data point on the bug itself: I have other Make scenarios with Glide “Add Row” modules that have run and tested successfully recently. So this doesn’t seem to be a blanket “Glide API is gated on my plan tier” issue — it looks specific to this scenario/module’s configuration or connection, since other Glide Add Row modules elsewhere in my account are working fine. Wanted to flag that in case it points toward a narrower cause (e.g. something about this specific table connection or field mapping) rather than a platform-wide restriction.
Second — and this is the main update: I ended up restructuring the app architecture in a way that removes the need for this particular automation entirely, at least for now. The original design required Make to pre-create a Support Relationships row for every user/artist pair so a list could read from that table. I changed the listener-facing list to source directly from the Artists table instead, with row creation happening on-demand (via a Glide-native workflow) the first time a user interacts with an artist, rather than being pre-populated. I tested this with both a brand-new user and a newly-added artist, and both flows work cleanly without any Make involvement.
So the urgency on my end has dropped — I’m no longer blocked by this specific bug for the user-facing app. That said, I’d still genuinely like to understand the root cause if you or anyone else in the community has insight, since I may use Make/Glide Add Row modules elsewhere later and would rather understand the failure mode than just work around it indefinitely.
Thanks again for your help getting this far — really appreciate the community support.
Best, Daniel PayMusicians
Hello @Daniel_Jenkins,
Thank you so much for well detailed response!
According to Glide’s Official Pricing listed here:
API is available starting on Business Plan so one above your current “Maker”.
Also this FAQ document states that:
But:
But this points the other way. So my guess: you’re either on some kind of legacy plan, or those other apps were created before the pricing change took effect.
Having above in mind I would dig into Glide.
Starting by checking other scenarios if they really add new row or only show success plus what I said ealier- duplicate/ create new scenario and play with one module only and hardcoded data.
What else you can do on Make? You can use DevTools Chrome Plug-in. It will allow you to see raw request – and whats more important – raw response. Make Apps can parse response and hide some informations.
If you need any help with devtools, please reffer to:
Or dm me.
Have a nice day,
Michal
