makeplane / makeplane/plane

Webhooks: double POST on specific activities, updated/created action confusion

Open
#7,249 3 comments 0 reactions 1 assignee View on GitHub

@NarayanBavisetti is already working on this.

Since Jun 23, 2025.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

I am not marking this as a bug as this might just be me not understanding how Plane behaves.

A) Double Payloads

If I update an existing work item changing it from In Progress to Done, I get two payloads.

  1. action: "updated" activity.field: "state"
  2. action: "updated" activity.field: "state_id"

This makes sense to me, it's basically saying "I've updated state" and "I've updated state_id".
The same happens for labels/label_ids, assignees/assignee_ids.

Now this is where I am struggling:

If I assign a Start Date to an issue, I also get two payloads, but they are exactly the same (only with a slightly different timestamp).

  1. action: "updated" activity.field: "start_date"
  2. action: "updated" activity.field: "start_date"

The same exact thing happens with target_date as well as priority.

Example

This seems to be a bug, but I am not fully sure and would love to get some guidance.

B) Created/Updated action confusion

When I assign priority/labels/etc to an existing Work Item, I get those in form of action: "updated".
When I assign a Module to an existing Work Item, I get this in form of action: "created"

The same exact thing happens when assigning Cycles.

I find this very confusing. Why is it not considered an updated action? Is the work item somehow duplicated in the backend when it is assigned to Modules / Cycles?

I also find this very confusing/inconsistent but I might just be missing some context.

Would love some guidance here as well.

Thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.