We are currently building an integration to realize a two-way exchange of data from SeaTable to our CRM system. Our problem is to have a defined trigger point so that Zapier tasks are not constantly generated.
For the direction CRM => Zapier => SeaTable we use a “save and leave” function in our web-based CRM. This means that a trigger that starts a transfer via Zapier to SeaTable only occurs when this action is started after completing work in the data in the CRM.
I would also have to implement something like this with SeaTable (which will tend to be the leading system for certain tasks in the future).
I was thinking of something like a button that sets a status when clicked, for example, which is then used as a trigger parameter.
However, since data records can also be adjusted several times, I would have to reset the trigger status so that the action can then take place again.
Is this something I can realize with automations in SeaTable or do I have to realize this with Zapier with an additional task.
Best Regards
Thomas