How do I make my Google Forms + OpenAI + Gmail automation more reliable for clients?

Questions
, , , ,
1

Hey Make community — looking for advice from
people who’ve built similar flows.

I built two automations for marketing agencies:

Automation 1 — Content Repurposing Engine
Google Forms → OpenAI (x5 modules) →
Google Sheets → Gmail

Someone submits a form with long-form content
and receives 5 platform-ready assets by email
in 60 seconds. LinkedIn post, Twitter thread,
Instagram caption, email newsletter,
and video script.

Automation 2 — Client Report Generator
Google Forms → OpenAI → Google Sheets → Gmail

Someone submits client data and receives a
complete 7-section professional report
by email in 60 seconds.

Both are working well in testing but I have
a few questions before rolling out to more users:

  1. What’s the best way to handle OpenAI API
    errors gracefully so the flow doesn’t
    just fail silently?

  2. Is there a better module than Google Forms
    for collecting input that works well
    with Make.com?

  3. Has anyone built a retry mechanism for
    failed OpenAI calls inside Make.com?

  4. I packaged both as downloadable bundles
    with the blueprint JSON included — is
    that something people find useful in
    this community?

Any advice appreciated — happy to share
the blueprints if useful to anyone here :folded_hands:

3

Welcome to the Make community!

OpenRouter

If you are referring to “Instant” Webhooks, you can create a script/function in Google Apps Script to trigger a Webhook request to a Make scenario.

If you are referring to other types of form integrations on Make, see https://www.make.com/en/integrations/category/form-builders-surveys?search=forms

Have you tried using error handlers?

Error directives can only be added to an error handler route

1. Right click a module and select “Add error handler”

262×200 13.4 KB

2. Error handlers will appear

755×540 27.2 KB

For more information on error handling, see:

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!

4

Hey Patrik, been doing pretty much this exact stack so a few thoughts.

For the OpenAI errors (your 1 and 3 kinda go together): the thing that saved me the most was just adding an error handler on the OpenAI module and using the Break directive. Break parks the run as an incomplete execution and retries it automatically on whatever interval you set in the scenario settings, so timeouts and rate limits basically sort themselves out instead of killing the run. For stuff you don’t actually want to retry (bad input, content policy, that kind of thing) I send it down a Resume branch with a fallback value so the Sheets/Gmail steps still finish, just with an “ai_failed” flag. That way nothing dies silently.

Related thing: I always dump failures into a separate Error Log tab (timestamp, module, error msg, raw payload). Sounds boring but honestly it’s the one thing that made these reliable once real users were on them. You can actually see what’s breaking instead of guessing.

On the form question, yeah I’d ditch Google Forms. It’s polling so it’s slower and the mapping is annoying. Anything with a native webhook (Tally, Fillout, Jotform, Typeform) fires Make instantly and gives you clean named fields. Tally or Fillout if you want cheap. I usually throw a quick normalization step right after the webhook so OpenAI always gets the same shape no matter which form it came from.

And on the bundle thing, there’s definitely interest, I’m doing something similar. Only catch is this place gets a bit twitchy about anything that smells like promo, so “here’s how it works” with the blueprint as a bonus goes down way better than a straight pitch. Happy to swap notes if you ever want.

5

Error handling:

[OpenAI Module] → Error Handler: Resume
  ├─ Add row to "Failed_Requests" sheet (timestamp, error, raw_input)
  └─ Send Gmail alert to yourself

Stops silent failures, logs and pings you instead.

Retries (set on OpenAI module, Advanced settings):

Retries: 3
Interval: 5s → 15s → 45s (backoff)
Retry on: 429, 500, 502, 503, 504

Covers rate limits and timeouts, which is most of what breaks.

Validate output before sending (Filter module before Gmail):

length(output) > 200 AND contains(output, "LinkedIn") AND contains(output, "Twitter")

Catches truncated/malformed responses before they hit a client inbox.

Forms: Tally or Typeform if you want better validation, same webhook setup in Make.

Bundles: Fine to share, just scrub sk- keys and hook. webhook URLs from the JSON first