Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

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? 

 

 

Hi @Roberto Melo 

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 @Troy Tessalone, thanks for the help.

 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?  

 

 

 

@Roberto Melo 

Can you post a screenshot with how the Filter conditions are configured?

 

HI @Troy Tessalone, it's a simple filter that validates if the Slack message has a key word (RAPPI) to trigger. 

 

 

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. 

@Roberto Melo

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 @Troy Tessalone , it's already FALSE: 

 

 

@Roberto Melo 

In the Slack action, make sure to set “Send as a bot?” = Yes.

 

@Roberto Melo 

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.

 

@Roberto Melo

In the Slack action, make sure to set “Send as a bot?” = Yes.

 

It's already sending as a bot. 
 

@Troy Tessalone In the GET result I have lots of MenuID, zapier is posting in the thread all results like an individual message. 

 

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 {}.

 

 

Reply


Terms & Conditions