Here are my instructions from Claude. Can someone help me connect a simple database from Retool to Make?
Retool has its own automation layer called Retool Workflows. You can configure a workflow that triggers when a new row is inserted into your Retool database table, then sends an HTTP POST request directly to your Make webhook URL.
This keeps everything inside Retool's ecosystem and requires zero database credential sharing. The setup is:
In Retool, create a new Workflow → set the trigger to "Database change" on your submissions table → add an HTTP Request block → paste your Make webhook URL → map the form fields as the JSON body. Make receives it exactly like any other webhook submission and your existing scenario runs unchanged.
I checked Retool Workflows and I don’t think there is a native “new row inserted in Retool Database” trigger.
But if the submission comes from a Retool form/app, you can handle it cleanly: after saving the data, trigger a retool workflow and send the form data via HTTP to Make there.
Worst case, use a scheduled workflow, check for new row, send them to Make and mark them as processed
I build these kinds of integrations quite often (usually for syncing leads or automating follow-ups), and this pattern works reliably.
If you want, I’m happy to take a look at your setup or help you wire it properly end-to-end.
@Filippo_Galli Thanks for your response. I am keeping it as a backup. I’m being advised by Claude to set up Supabase as my new CRM of record that interfaces with Make. I haven’t set it up yet. But this is helpful as a backup. I’ll let the Retool community know how it goes when I do the work.
Unfortunately, Retool does not have a built-in "new row in database" trigger for your use case.
That being said, I would try out the suggestions that @Filippo_Galli had mentioned, or if you have any questions when setting up Supabase to interface with Make please let us know!
I want to close the loop on my experience trying to do this with Retool agent’s Assist. I finally am going to market after intense vibe coding sessions in May and early this month. Retool’s agent was struggling in major ways with successfully configuring a workflow that was successful in sending data to Make. We built two different scenarios. I had my Claude agent conferring with Retool Assist to connect first my HubSpot database, that didn’t work. So after so many failures, I stopped the merry-go-round and tried Google sheets, which Claude recommended and we were successful in getting successful pings in Make, but then the data from the Retool app never populated fully. One of the most significant difficulties has been the inability to share screenshots (Mac-generated) with the Retool Assist agent. Prior to Make, I tried to connect the data from the app to my SharePoint. That was a nightmare. Finally, I am going to market with an app that is usable online, but there is no ability to download a pdf version, even though it was possible at one point in the build process. I think part of the issue is that I built my tech stack analysis app right before the new app builder came out. I did build smaller, related business analysis apps that worked well and delivered impressive email results to users. I added them in my “suite” of apps. But currently, they are not integrated in the way I would want. You will see that the dashboard is still using sample data. I need to change this too before sending to warm leads. https://emediaprose.retool.com/embedded/public/3fd3c9e2-75cb-474b-897e-8177ec46076c/client-intake
At this point, I am really inclined to take the tech stack audit tool to the new app builder and try to integrate all the audit modules in a true suite. I know this is not working.