Custom App Dedicated Webhook URL returns HTTP 410 during webhook verification

Questions
1

:bullseye: What is your goal?

I’m developing a Custom App in Make using an Instant Trigger paired with a Dedicated Webhook.
Workflow:

User creates a scenario and selects the Instant Trigger.

User clicks Create Webhook.

Make generates a webhook URL using {{webhook.url}}.

The generated webhook URL is sent to my application during webhook registration.

My application performs mandatory webhook URL verification before creating the webhook.

:thinking: What is the problem & what have you tried?

Webhook creation fails because the generated Make webhook URL returns HTTP 410 Gone during verification.

I tested the generated webhook URL directly in Postman with a POST request and got the same 410 Gone response.

Confirmed:

{{webhook.url}} is generated successfully.

The URL is passed correctly to the provider.

The provider can reach the URL.

DNS and SSL are working correctly.

The same verification process works with other app endpoints.

The issue only occurs with the Make-generated Dedicated Webhook URL.

:clipboard: Error messages or input/output bundles

Error returned:

Unable to verify the provided URL, Please verify that your service is running.

Debug output:

verifiedUrlStatusCode: 410

Postman test:

POST https://hook.eu2.make.com/xxxxxxxxxxxxxxxx
Response: 410 Gone

3

@Thalapathy
Hi Thalapathy,

HTTP 410 Gone on Make Dedicated Webhooks is almost always a timing/lifecycle issue inside your Custom App’s attach communication block.

In Make Custom Apps, a generated {{webhook.url}} stays in a detached / 410 Gone state until Make’s backend successfully completes the attach API call with your external provider.

Here is why you are hitting 410 and how to resolve it:

The Root Cause

If your external application attempts to verify the URL during the API call triggered by Make’s attach block, Make’s internal routing table hasn’t marked {{webhook.url}} as active yet (because the attach request hasn’t finished returning 200 OK to Make). When your app pings Make to verify during that window, Make returns 410 Gone.

Steps to Fix & Test

  1. Test with “Re-determine structure”:
    Go to a test scenario in Make, right-click your Custom App’s Instant Trigger module, and click “Re-determine structure”. While it’s actively listening, try sending the Postman request or triggering your app’s verification. This temporarily forces Make’s routing table to listen on that URL.

  2. Check your attach Communication JSON:
    Make sure your attach block in the Custom App Developer Console isn’t relying on a synchronous verification handshake before returning.

  3. Verify Challenge/Params Handling:
    Does your provider verify via GET (like Meta/Slack challenge) or POST? If it requires a challenge response, you need to configure the Webhook Communication tab in your Custom App to return the challenge parameter automatically.

If clicking “Re-determine structure” removes the 410 error during your Postman test, it confirms your provider’s verification is firing before Make marks the attach handshake as complete.

Let me know what your attach JSON block looks like if you need help tweaking it!

4

Hello Telepathy

Since you’ve already tested with both Custom Webhook and Twilio triggers, rebuilt the scenario, and even reproduced it in a new scenario, this doesn’t look like a simple module configuration issue.

One thing I’d be curious about is whether the dedicated webhook has actually been activated before the verification request is sent. Have you checked if Make expects the webhook to be attached to a running/listening scenario before it will accept incoming requests? A 410 response usually indicates the endpoint exists but is no longer available, so it makes me wonder if the webhook is being invalidated before verification completes.

5

@Jane_Form hey jane, good catch on the scenario listening state.

HTTP 410 on make dedicated webhooks almost always means make’s edge router marked the endpoint as invalidated — usually because the scenario wasn’t actively listening during the handshake, or the hook got detached from the custom app config.

what usually fixes it:

  1. hit “Run once” on the scenario so it’s in active listening mode before firing the verification.
  2. trigger the verification request from twilio/external service while it’s waiting.
  3. if it still throws 410, delete the old webhook entry in make’s Webhooks tab and generate a fresh one to force make to re-register the route on their end.

let me know if re-generating a fresh hook while in “Run once” mode solves the 410 for you!

6

Hey Gabriele

Thanks for the clarification! That explanation about Make’s routing lifecycle makes a lot of sense. I appreciate you taking the time to explain it. I’ll be interested to see whether putting the scenario in Run once mode and regenerating the webhook resolves it for the OP.