Plugins stop-start triggers | Pod | Add property selection in pod for filterCreatedAfter
{"ops":{"insert":"currently the "},{"insert":"filterCreatedAfter","attributes":{"code":true}},{"insert":" property on trigger looks at when the Message is created in the pod. This is an issue when doing the initial import with a plugin, which would cause the triggered plugin to trigger once for each message in the initial import"},{"insert":"\n","attributes":{"block-id":"block-41b02360-5c1b-466b-822f-9f18be6498cf"}},{"insert":"\n","attributes":{"block-id":"block-c1ea46d7-abdd-4e21-8972-7991c85b0660"}},{"insert":"TODO add a property to trigger that tells "},{"insert":"filterCreatedAfter","attributes":{"code":true}},{"insert":" which property to look at, so we can filter on "},{"insert":"dateSent","attributes":{"code":true}},{"insert":" instead. "},{"insert":"\n","attributes":{"block-id":"block-ec5db1da-d4b7-4a33-9239-38fe9b9b99e3"}}}
Stop plugin from running continously 1 small change json
┆Issue is synchronized with this Clickup by Unito
┆Ticket type: