Here my zap needs to be silenced for lets say 15mins
The action trigger is “new post in a private channel” for slack.
After the trigger gets initiated, the tricky part is not to get triggered for any messages in slack for the next 15 minutes while at the same time need to run my action steps without any hindrance.
Any possible workaround on this? please let me know
Best answer by SamBView original
Ah I see! Apologies, I thought you were wanting the Zap to trigger for a new message, and have it carry out certain actions but not carry out those same actions for any new messages that then trigger the Zap within the next 15 mins (I was thinking that the subsequent messages would be in relation to the one that triggered the Zap).
You wouldn’t be able to completely stop a new message from triggering the Zap unless the Zap was off. You could use the Zapier Manager app, as Troy suggested, with a Delay action to temporally turn off the Zap for 15 mins then turn it back on again. While the Zap is off though it wouldn’t see any of the new messages that would have triggered the Zap during the time that it was off.
With the Delay after queue action the Zap would trigger for each new message but would delay the actions from running until 15 minutes later. You can find out more about using it in our guide here: Delay after queue
That said, to stop the messages from triggering the Zap maybe we should be looking more at which type of messages should be triggering the Zap. For example could you use a specific phrase or emoji in messages that you want to trigger the Zap? Which would then allow you to use a Filter to check for it (Add conditions to Zaps with filters). That way, only messages that contain that phrase/emoji will allow the Zap to carry out subsequent actions. I’m suggesting a specific phrase or emoji within the content of the message, rather than to use the New Reaction Added trigger as it would only see reactions to messages within public not private channels.
Do you think using a Filter would work here?
Hmm, perhaps you could create a record of the message in a spreadsheet, using an app like Google Sheets for example. In the row for it you could put details for the message and add the words “on hold” in a column called “status” on the spreadsheet for that row. Then you’d use a Filter by Zapier action to check whether the Zap should continue to run or halt any subsequent actions. And you’d have a separate Zap that runs when a new row is added, waits for 15 mins then removes the “on hold” status.
Zap 1 - creates a record of the message in a new row and marks it as “on hold”
Zap 2 - removes the “on hold” status from the row after 15 mins
Do you think that approach could work?
The method you described is good though. However the tricky part is that it only applies on message from the past as when a message comes up, we set new record if it doesn’t exist and updates on hold in the next row and filters out with if zap search is false, then continue( which means if the message is already sent before, it stops the zap from running any following subsequent actions).
How to make it work so that any newly added message shouldn’t be triggered into the zap1?
Hope you got my idea!
Thanks for letting us know what worked for you!
If you need further assistance in the future, feel free to post and we’ll do our best to assist you! 😊
Thanks for letting us know!
Have you tried using Delay by Zapier (Delay after queue) after the trigger step? Please let us know if this works for you! 😊
More about Delay after queue here: https://help.zapier.com/hc/en-us/articles/8496288754829-Add-delays-to-Zaps#delay-after-queue-0-2
You may want to consider using the Zapier Manager app with the Turn Zap On/Off action.