3
Feature Request: Manual "Save" button or batch update trigger for Webhooks (n8n automation)
Source: twentyhq/twenty#20706 · opened by @n2ojim
Scope & Context Example: Current behavior Currently, Twenty relies on an instant auto-save mechanism. Every time a user modifies a single field, the record is immediately saved to the database, and a record.updated webhook is dispatched instantly. If a user needs to update 3 different fields to provide the necessary context for an n8n automation, 3 separate webhooks are fired sequentially. The external automation is triggered on the very first field change, receiving incomplete data because the user hasn't finished filling out the other fields yet. This results in failed automations and unnecessary compute/credit usage on external tools. Example: Expected behavior Users should be able to modify multiple fields and ensure the external webhook receives the full, completed state of the record in a single batch. We need a way to commit changes globally or trigger the webhook manually. This could be resolved in a few ways: 1. Manual Save Mode: A toggle or mode where auto…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add easier integration to n8n, zapier, make and easier custom workflows
5 votes · 0 comments
Guide to success for this project. Invoicing, Stable/pre-release, automation, Messaging.
4 votes · 0 comments
[Idea] Native Marketing Integrations: Meta Ads & Google Ads for Lead Capture and Attribution
3 votes · 0 comments
N8N Integration
33 votes · 0 comments
Button field
1 vote · 0 comments
No comments yet.