Skip to main content

An suggestion to add some fileds to configure the http automation

 

when i set it to send sometimes it retry a lot of times in a short period of time if the response isnt 200 ok

 

Then configure retry time in seconds before retry again can solve it if the api delay to response

Configure the amount of retries to do not expend a lot if there some problem on the integration api

Configure if you want to retry just if the response code status is equal to  a list of status setup by the admin, i.e. if the return status is 400 bad request maybe is a problem with the request… maybe dont make sense retry it, same to 2xx obut i thing the 1st suggestion is better to solve this for 2xx] but to 404 can be a temporary problem, same to 500 depending on the api

 

today to try solve it im adding a field to save the htt response and add ‘when card move to a phase AND field XXX is not filled’ but dont solve at all if the people try to restart the automation moving the card again and…. i need another thing to acept retry moving card… and i need to create a lot of exceptions to allow retry moving the card again to do not create more complexity to the user

Good Idea 

Great idea!!!

That’s what i’m talking. Great idea! 👍🏻

Hey @Marcelo Araujo , thanks for bringing that up!
This makes sense, and we have some plans to add more integration capabilities into the product in the near future, that should solve that scenario by allowing you to build a full logic of what is needed in your integration, with error treatments and delays available to be used, for example. We will let you all know here in the community when we enter the beta phase of that!
For now, using the pipe fields and other automations to achieve the desired outcome is the best option indeed.

New→Submitted
Terms & ConditionsCookie settings