Hello folks,
I'm using slack message as a trigger to make an API call, get the result and post it back in the slack thread, using the timestamp.
Although, it's generating a huge response, like if it was triggered +30x.
Any idea why this is happening?
+14
Hi
Good question.
Please clarify with screenshots which specific Slack trigger event you are using.
It’s likely that the Zap action is also the Zap trigger.
Hi
I'm using this trigger:
The message must contain a key word for the automation to proceed.
The final response doesn't contain the key word to proceed, I mean, the response cannot be a trigger.
By checking the historical, I see the exact same trigger +30 times, like if it was receiving 30 triggers from slack.
QQ: The response to the trigger is a GET result from an API, I thought maybe changing "Send As JSON" to TRUE would help, because sometime the GET can be really large and slack is kind breaking. But no idea how to use the "JSON key". Can you help with?
+14
Can you post a screenshot with how the Filter conditions are configured?
HI
This is how I see the +30 triggers on the history + filter validated.
Triggers:
I really think this is because of the API GET result, the amount of requests/triggers usually matches with the # of {} result in the get.
in this case, it triggered 420 times.
+14
In the Zap trigger step, make sure the “Trigger for Bot Messages?” = No.
In the Slack action, make sure to set “Send as a bot?” = Yes.
Hi
+14
In the Slack action, make sure to set “Send as a bot?” = Yes.
+14
Thread replies include additional fields that you can use as conditions in the Filter step.
e.g. thread_ts does not exist
Logic would be to only continue for main messages, not thread replies.
In the Slack action, make sure to set “Send as a bot?” = Yes.
It's already sending as a bot.
If there's "menuID" 10x, I get 10 replies. It seems zapier is not considering the json result as 1 file, but as individual reponses.
The response on Zapier is not the full json, but the first array {}.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
