Skip to main content
Solved

HTTP Caller Sending Too Many Requests (Slack Webhook)


I am running a workspace that detects changes in data between an API and Web App and applies only updates to the Web App using a change detector transformer. I am sending a notification to a Slack Webhook but instead of a single HTTP request being made, it makes 1 request for each data record updated.

 

What I Want:

"Successfully updated 70 records".

 

What is Happening:

"Successfully updated 1 records".

"Successfully updated 2 records".

And so on till 70...

 

Is there a transformer that will allow me to sum the number of updated records and only send a single HTTP request to the Slack Webhook?

 

Workbench Screenshot:

Workbench Screenshot 

Thanks!

Best answer by oscard

You could use the transformer FeatureCounter followed by a Sampler of just one feature.

Or you could use the StatisticCalculator. There you have a function for total count of features.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

oscard
Influencer
Forum|alt.badge.img+22
  • Influencer
  • Best Answer
  • October 14, 2021

You could use the transformer FeatureCounter followed by a Sampler of just one feature.

Or you could use the StatisticCalculator. There you have a function for total count of features.


oscard wrote:

You could use the transformer FeatureCounter followed by a Sampler of just one feature.

Or you could use the StatisticCalculator. There you have a function for total count of features.

Thanks very much. Both methods were acceptable. I used the StatisticsCalculator as it's simply a transformer less.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings