Skip to main content

Hi, I am setting up a new support portal, and started an Enterprise Trial so that we would have access to application requests so that we can hit our custom API. After setting up an app request, testing it successfully (“Test Successful”), and the status is “Ready,” it is NOT surfacing when selecting the “Select app request” action in a new macro/rule workflow. See the screenshots below.

This is the app request, showing “Ready” status:

 

And when creating a new macro, it keeps telling me to setup a new application request, because it cannot find the ones I have created:

Is there something wrong with my account setup? Why can’t I use the app requests in rules/macros?

Based on the title of the App Request you created I’m assuming that’s a GET request. GET requests cannot be used in the Send App Request step of your Macro flow builder. Only POST, PUT, PATCH, or DELETE request methods can be used there. GET requests can only be used when creating a Dynamic Variable within a Macro (look at the bottom of the flow builder you should see a “Dynamic Variable” button). 

Can you please clarify a bit on your overall workflow here, and why you need to fire off a GET Request as a result of a Macro being triggered? 


Hi Andy,

Thanks for the clarification. You are right, I was using a GET request, and the app request does surface in Rules/Macros when changing to POST.

Question — I am trying to pull information from our external servers, such as custom variables, e.g. a reset password link, accounts status, etc, by using a rule or macro. Does that mean I need to use POST just to get account information? That works but I don’t understand why GET is not supported.


Yes, this should still be possible. GET App Requests can still be used within a macro, but only from within a Dynamic Variable. The reason for this restriction is that a macro or rule execution is expected to produce an action (Create, Update, or Delete) so GET requests are not allowed as the direct result of a rule or macro triggering.

Here’s a screenshot of what a GET App request dynamic variable might look like:

 

You would then use this dynamic variable somewhere within your Macro. A good use case for this type of dynamic variable would be retrieving some data from an outside source and presenting in Front as a comment. Like so: