📌 Need Help: Webhook Data Missing After Detach – Bug or Feature?

How To
, ,
1

Hey Make.com community! :wave:

I’ve been developing apps for a while, but I’m pretty new here, just getting started with Make.com—and I’m seriously loving the possibilities! No-code/low-code is an absolute game-changer, and I’m already brainstorming ways to build cool Make.com apps that can help other users make the most out of the platform.

As I’m diving deeper into Make, I ran into something unexpected while working with webhooks, and I’d love to get the community’s take on it. Maybe I’m missing something, or maybe this is something we can improve together!

I know a lot of experienced folks here have worked with webhooks extensively, and I’ve come across some great insights in previous discussions. @DanBorn, I’ve seen some of your responses on webhook-related topics, and they’ve been super helpful. If you have any thoughts on this, I’d really appreciate your input!

:face_with_monocle: What’s Going On?

When I attach a webhook, I get all the expected data. But when I detach it, suddenly some key properties disappear. This makes it really tricky to manage webhook lifecycles properly.

:mag: Quick Breakdown

Step 1: Webhook Attach (All Good :white_check_mark:)

{
    "webhook": {
        "id": 2076656,
        "name": "My Webhook",
        "udid": "jnv2i0smum9vw804chavn0ugfrk0ax1z",
        "url": "https://[webhook-url]",
        "type": "web",
        "theme": "#ea89bf",
        "editable": false,
        "flags": {},
        "data": {
            "__IMTCONN__": 3962044
        }
    }
}

Step 2: Webhook Detach (Wait… Where Did Everything Go? :exploding_head:)

{
    "webhook": {
        "__IMTCONN__": 3962044,
        "teamId": 711933
    }
}

:hammer_and_wrench: What I’m Sending

Just to be sure, here’s the JSON payload I’m sending when testing:

{
    "url": "{{common.serverEndPoint}}",
    "method": "POST",
    "headers": {
        "apikey": "{{common.supabaseAnonKey}}",
        "Authorization": "Bearer {{connection.supabaseAccessToken}}",
        "Content-Type": "application/json"
    },
    "body": {
        "url": "{{webhook.url}}",
        "name": "{{webhook.name}}",
        "type": "{{webhook.type}}",
        "webhook_udid": "{{webhook.udid}}",
        "flags": "{{webhook.flags}}",
        "theme": "{{webhook.theme}}",
        "editable": "{{webhook.editable}}",

        // Just to see what Make.com returns if I reference the entire webhook object
        "webhook": "{{webhook}}"
    }
}

It seems like some fields are just missing when detaching the webhook, which makes it really hard to track and manage them properly.

:x: Why This is a Problem

  • Makes tracking webhook lifecycles difficult
  • Hard to automate cleanup processes
  • Could lead to orphaned webhooks in production
  • Breaks automations that rely on consistent webhook data

:bulb: How Do You All Handle This?

Since I’m still learning the best practices in Make.com, I’d love to get some insights from the experienced folks here:

  1. Is this expected behavior, or is something off?
  2. How do you handle webhook detachment in a way that keeps everything consistent?
  3. Any best practices for making sure webhook data persists properly?

:rocket: Looking Forward to Your Thoughts!

I know there are some brilliant people in this community who’ve probably worked through this before, so I’d love to hear your insights!

If anyone has experience with this—or even ideas for a workaround—I’d love to hear your thoughts! Thanks in advance! :blush: