Enhance Webhooks

[paulyili]

Current behaviour

You can select an Object then select an Action.

Suggested Behaviour

Add a 3rd option (multi select) to select the field(s) of the selected object. This would mean that drop down will need to auto populate with the objects fields.

This minimise webhooks when just selecting and editing the Object.

Usage

Sending webhooks to update email marketing platform E.g People - Tags (custom field) - Update

Add tags to a person, then to update into an email marketing platform. If person is not in email marketing platform, creates a person.

If you update another field, the webhook still triggers the automation. You can create a filter to see if there's any tags. if no tags, you can stop the automation.

But if you decide to remove the tags from the person, webhook is triggered, but automation stops as your filter's condition to stop on no tags and all tags will stay in the email marketing platform. Which means you now need to add checks to the automation to avoid this.

If someone is using Zapier, n8n etc, the flow will be quite complex for a simple task.

[skyfox675]

Would love this feature!

[Bonapara]

Great point @paulyili, thanks!

We want to display another row under the first webhook filter row as soon as the first filter is modified.

https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=34845-126796&node-type=frame&t=tbVAhqYMdCJHneqF-11

Technical input

• Make a command to migrate the data
• We should rename operation in operations and make it an array
• Make the front-end

As some backend is involved, this issue is for an experienced contributor. @ehconitin do you want to handle it?

[ehconitin]

🫡

[martmull]

@paulyili @skyfox675 I suppose this feature will solve your issue https://github.com/twentyhq/twenty/issues/6071 For update event, we send the updatedFields info in the event

What do you think?

[martmull]

@Bonapara here is the multiple operation ticket -> https://github.com/twentyhq/twenty/issues/7792

[martmull]

Closing that issue as it will be addressed in those tickets. @paulyili @skyfox675 Feel free to reopen the issue if you are not satisfied with the solution provided in https://github.com/twentyhq/twenty/issues/6071