Whatsapp API isue

Hire a Pro Hire Help
1
  1. Webhook not triggering consistently
  2. Need error handler on HTTP 6
  3. Need scenario to stay active 24/7
1 Like
3

Hello @Sunday_App , 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

4

Hey @Sunday_App , I can fix all three issues by hardening the scenario at the trigger, request, and recovery levels. I’d first audit the webhook delivery path and scenario settings to identify why triggers are being missed, then add proper logging, retries, and fallback handling so HTTP 6 errors don’t break the flow. For 24/7 reliability, I’d review scheduling, execution limits, webhook response timing, and scenario health checks to keep it running consistently. If needed, I can also add alerting so failures are caught before they impact operations. Send over the scenario structure, webhook source, and the module where HTTP 6 occurs, and I can start troubleshooting immediately. You can book a call here to discuss this further

5

Hi @Sunday_App ,
I can help you handle the issues mentioned.
Please connect further, If still hiring

Regards
Deep

6

Hi!

I see you’re struggling with inconsistent webhooks and HTTP errors. These are usually not “glitches” but specific configuration issues (like missing 200 OK responses or rate limits). I can fix this and make your scenario bulletproof.

What I’ll do to stabilize your build:

  • Fixing Webhook Triggers: I’ll ensure your landing page/source gets an immediate Webhook Response (200 OK). Without this, many services stop sending data because they think your scenario is dead.

  • Handling HTTP 406: This error usually means the server doesn’t like the “Accept” headers or the data format. I’ll debug the raw HTTP request and fix the headers so the connection stays solid.

  • 24/7 Reliability: I’ll implement a Global Error Handler (using Break/Resume or Ignore routes) so one failed request doesn’t turn off your entire scenario.

  • Logging: I can set up a simple log in Google Sheets or a DB so you can see exactly why a specific run failed, without digging through history.

Why me? I’m a developer at heart (JavaScript/Python). If a standard Make module fails, I can write a custom API request to get it done.

Portfolio: https://mikedevai.netlify.app/

Contacts:

  • Telegram: @hely_chatbots

  • WhatsApp: +375293761570

8

Hi Sunday — happy to help debug. WhatsApp API issues in Make.com almost always trace back to one of these (in rough order of frequency):

  1. Webhook signature verification failing silently (the Make HTTP module doesn’t always surface this clearly)
  2. Token refresh — Meta access tokens expire and Make doesn’t auto-handle the rotation
  3. Template message rejections from Meta’s policy review (especially anything that looks promotional)
  4. Rate limit hits when the scenario fires on a webhook burst
  5. Phone number quality rating dropped, throttling all sends silently

If you can share:

  • A screenshot of the error in Make’s scenario history
  • Whether this just started or has been ongoing
  • Whether outbound sends, inbound receives, or both are affected

…I can usually pinpoint it within a 30-min call. I’ve built WhatsApp automations end-to-end (Business API integration, NLP-driven response, CRM sync) so the failure modes are familiar.

Email me at priyanshukumarmaurya2224@gmail.com with the above and I’ll send a calendar slot for tomorrow.

— Priyanshu
linkedin.com/in/priyanshu-axiom