I"m trying to find where to hire a pro... there is only the pinned info ... but I can't see how I can find someone and get in contact with them

Looking for someone to fix emergency scenarios. preferably somone in europe / uk so we are on the same time difference.

Many thanks

2 Likes

Hi, I can help fix your emergency scenarios quickly. I’m experienced with troubleshooting and stabilizing Make/n8n automations and can jump in to diagnose and resolve the issue fast. Feel free to share the scenario details and I’ll take a look right away. you can schedule a call with me here to further discuss this.

Hello @Gennaro_Capriglione , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

Hi Gennaro,

I’m based in the EU.
You can leave me a message here or put some time in to my calendar here.

I am a expert level Make developer, and I sure able to fix issues you may have around errors, APIs, Webhooks, scenario timeouts, functional logic, etc

Cheers
Genesys Automation

Ciao @Gennaro_Capriglione ! I would love to help you with your scenarios

We are a small team of make.com experts and have developed plenty of complex integrations. We have part of our team based in Europe so communication should not be an issue.

If you are interested we would love to help you, you can schedule a call in here: https://cal.com/aspirity/discovery?utm_source=make discovery or check our website www.aspirity.com

Hi @Gennaro_Capriglione,

I came across your requirement regarding fixing scenarios.

Recognized as a Make.com Contributor :star::star: status, certified in Make.com and Airtable with my background of 5+ years building CRM architecture and workflow automation, working with 100+ clients and delivering 1000+ hours of reliable automation systems.

Relevant automation examples and past Make scenarios can be shared upon request.

Portfolio: https://www.upwork.com/freelancers/~013d3dfad191c75b82?mp_source=share
Meeting Link: https://calendly.com/proboticsolutions/30min

Please let me know a suitable time to connect. I’d be glad to discuss your setup and recommend the best approach.

Hi Gennaro,

I can help with this.

I work extensively with Make.com and have experience troubleshooting and repairing broken or urgent scenarios, including issues with modules, API connections, routers, filters, and webhook triggers.

If a scenario has stopped working or is producing errors, I can:

  1. Quickly review the scenario to identify the failing modules
  2. Fix broken mappings, API errors, or missing fields
  3. Test the scenario to confirm it runs properly again
  4. Add basic error handling to prevent future failures

Even though I’m not in the UK/EU timezone, I’m responsive and can usually jump in quickly when something breaks.

If you’d like, you can share:

The scenario blueprint (JSON export)

A screenshot of the error message

A quick description of what the scenario should do

You can also reach me directly at:
fopefoluwaakinola@gmail.com

Happy to help get your scenarios running again.

Hi Gennaro, welcome to the community.

If your scenarios are failing or getting stuck I can take a quick look. Most emergency issues

I see in Make usually come from things like webhook failures, API limits, or broken routing logic.

If you want, share a bit about what’s happening and I can help you diagnose it.

Portfolio: View my past automation works here.

Book a call: Click here book a walkthrough call session (P.S Kindly adjust to your timezone before booking)

Email: folafoluwaolaneye@gmail.com

Best regards,

Folafoluwa Stephen

Hi Gennaro,

I can jump in on emergency Make scenario fixes and I can work on Europe hours.

When a scenario is already breaking in production, the fastest path is usually to isolate the failing modules or webhooks, patch the auth or mapping issues, and then add proper retries and error handling so it stops failing again the next day.

If you want, send the failing scenario summary or screenshots here and I can tell you quickly whether it is a same-day fix or a larger cleanup. I am happy to work async if that is faster than scheduling another intro call.

Hi Gennaro, I’m manny - london based here, so timezone is perfect.

Before jumping on a call, a few quick questions that’ll help me understand the urgency:

  1. What’s breaking? Is it a webhook timing out, a module throwing errors mid-scenario, or is the whole scenario just stopped running?

  2. How many scenarios are affected? If it’s one critical path vs. multiple, the fix approach is different.

  3. Are you seeing specific error codes? Common emergency culprits: 429 (rate limiting), 401 (expired auth), or connection timeout on third-party APIs.

Some quick things that could work in the mean time:

  • Check Scenario > History for the exact error log. the “Show bundle” view usually reveals the root cause faster than the summary

  • If it’s a webhook scenario, verify the webhook URL hasn’t changed (Make regenerates these sometimes after plan changes)

  • If a module is failing intermittently, try adding an Error Handler with a Resume directive. this keeps the rest of the scenario running while you debug

I specialise in Make and n8n automation for small businesses. I’ve built everything from CRM pipelines to care coordination workflows. Happy to take a look at the scenario today if you share the details above.

Here’s my calendar if you’d rather talk through it: cal.com/manny-amoah-iys902/30min

Have a good day

Manny

Hi Gennaro,

I am Priyanshu Kumar, Founder of Evara AI (incubated at IIT Bhubaneswar). I understand the urgency – when scenarios break in production, every hour of downtime matters.

I have extensive experience debugging and fixing Make.com scenarios under time pressure. The most common emergency culprits I encounter are expired API authentications, webhook URL changes after plan modifications, rate limiting from third-party services, and broken module connections after app updates. I can typically diagnose the root cause within the first 30 minutes of looking at the scenario history and error logs.

Regarding timezone: I am based in India (IST, UTC+5:30), which gives us a solid overlap with EU/UK working hours. I am typically available from early morning IST, which maps to late morning through afternoon in the UK/Europe timezone. For emergency fixes, I can be flexible and adjust to match your working hours.

If you can share the specific scenario details – what is breaking, the error codes you are seeing, and how many scenarios are affected – I can give you an honest assessment of the fix timeline before we commit to anything.

Feel free to DM me here and I can take a look today.

Best,

Priyanshu Kumar

Founder, Evara AI

Hey @Gennaro_Capriglione,

Have sent you a DM as well. Would love to help you for automation support. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency. I have worked with multiple European companies so timezone will not be an issue.

Some of my relevant work-
• For an education company, I integrated LearnWorlds with Airtable, Make, and Pipedrive via API handling complex pagination and syncing data in real time.
• For a digital agency, I set up a smart call-routing system using Twilio, Airtable, and Zapier fully automating lead handling.

I can understand how it can become more technical and difficult to handle integrations. I am a Make advanced certified with a background in computer science so quite comfortable in integrating API and custom code. Would love to talk more about the project :slight_smile:

Happy to also jump on a call if it’s easier.

Cheers,
Sparsh
Founder
Automation Jinn

Hi there,

I saw your post and I’m ready to jump in. I’m an automation engineer based in Europe (UTC+3), so I’m on your schedule and can start troubleshooting immediately.

How I can help right now:

  • Fixing Broken Flows: I specialize in finding those “hidden” errors in n8n and Make scenarios that stop production.

  • Error Handling: I’ll not only fix the current bug but also add error alerts and retries so this doesn’t happen again.

  • API & Webhook Audit: If your data isn’t reaching its destination, I’ll find where the handshake is failing.

I’ve handled “emergency” cases for high-traffic CRM and lead-gen systems before. I know how to work under pressure without breaking the rest of your architecture.

Portfolio: https://mikedevai.netlify.app/ Contact me for a fast fix: @hely_chatbots (Telegram)

i am interested to help and build amazing automation systems

try Fiverr to find available resources