[BUG] in Make.com - Update a member webhook also triggers for new member

[Zeit08]

Issue Summary

I noticed that creating a webhook for “member.updated” makes the webhook trigger even when a new member arrives…

Is it only me? I am using this hook in Make.com I see the logs of what has been passed from this webhook.

Not sure if this is a Ghost bug or a Make.com bug.. please advise. Eventually seems like Make is using Ghost webhooks...

See here below, created_at and updated_at (both previous/current) have the same time

Steps to Reproduce

when a new member signs up, the webhook member.updated still activates. To see this you just need to listen to updated.member make.com webhook and register as a new user to your ghost website

Ghost Version

Latest

Node.js Version

nd

How did you install Ghost?

Pikapods

Database type

MySQL 5.7

Browser & OS version

No response

Relevant log / error output

{
  "member": {
    "current": {
      "id": "memberidhere",
      "uuid": "iremovedthisuuid",
      "email": "[email protected]",
      "name": "Name",
      "note": null,
      "geolocation": "{redacted"}",
      "subscribed": true,
      "created_at": "2025-04-23T14:54:13.000Z",
      "updated_at": "2025-04-23T14:54:13.000Z",
      "labels": [],
      "subscriptions": [],
      "avatar_image": "redacted",
      "comped": false,
      "email_count": 0,
      "email_opened_count": 0,
      "email_open_rate": null,
      "status": "free",
      "last_seen_at": "2025-04-23T14:54:13.000Z",
      "newsletters": [
        {
          "id": "redacted",
          "name": "Newsletter",
          "description": "",
          "status": "active"
        },
        {
          "id": "redacted",
          "name": "Newsletter2",
          "description": "",
          "status": "active"
        }
      ]
    },
    "previous": {
      "last_seen_at": null,
      "updated_at": "2025-04-23T14:54:13.000Z"
    }
  }
}

Code of Conduct

• I agree to be friendly and polite to people in this repository

[vikaspotluri123]

Topic on the forum: 57034

Since the member is joining from the frontend, the last_seen_at job is triggered, causing an updated event soon after a created event