Nobody talks about the production side of Make.com client work. Help!

Hey everyone! 👋

I've been learning Make.com for a while now and honestly the building part is fun — I get it, I enjoy it. But the moment I try to deploy for a real client? That's where I hit walls I didn't expect.

Currently working on what should be a simple project — Gmail → OpenAI → Gmail email summarizer. Works perfectly in testing. But moving it to production for a client is a whole different story.

Here's where I'm stuck:

🚧 The GCP OAuth verification process is taking forever. Branding needs to be verified before data access can be verified. Gmail scopes are sensitive so Google takes weeks to review. Meanwhile my client is waiting.

🤔 I'm also unsure about the right way to set things up professionally:

- Should everything be under the client's own Google/Make accounts?

- How do you handle GCP setup with non-technical clients?

- Is Google Workspace the real game changer here?

- How do you structure Make organizations for client work?

For those of you deploying Make automations for clients regularly:

1. What's your actual deployment process from finished scenario to fully live?

2. How do you handle the GCP OAuth verification issue?

3. How long does a proper client deployment take you realistically?

4. What do you wish someone had told you before your first client deployment?

Any real-world experience would mean a lot right now. The tutorials show the building part but nobody talks about the messy production deployment side of things!

Thanks so much 🙏

10 comments

Nobody talks about the production side of Make.com client work. Help!