Scripted REST vs Flow Designer asynch trigger for inbound messages

[John Pearson]

I need to create an api to handle incoming REST messages. It looks like I could either use a Scripted REST API or Flow Designer using a "REST API - Asynchronous" trigger. Which is the preferred way to do it? What are the pros and cons of each? Or is it just personal preference?

[MrMuhammad]

@John Pearson 

The main difference is Flow Designer Rest API trigger provides more intuitive way to manage the start conditions and designing the process flow. On the other hand, Scripted rest API's requires complex scripting that is hard to maintain in the long run. I'd prefer to design it via REST API - Asynchronous tigger and leverage the ability of flow to parse the objects and set values etc in a more manageable form.

Regards,

Muhammad

[Rohit Sarkar1]

If you want a low maintenance and easy configuration setup go with Flow designer approach however if you know your requirement might get snowballed to a much complex design in the future then the bet would be to use Scripted REST API to handle the logic in script.

[Maik Skoddow · Accepted solution]

Hi @John Pearson 

there are two main differences when using REST API trigger with Flow Designer:

1. This feature requires an Integration Hub Enterprise subscription!
2. You cannot send back a response body to the requester as you are used to with the scripted REST API.

On the following two articles created by me you can more information to this topic

• Platform: Integration Hub || Knowledge & Troubleshooting Resources
• Platform: Flow Designer || Knowledge & Troubleshooting Resources

Maik

[John Pearson]

All the responses were helpful, but I chose this as the answer because it specifically called out the issue with not sending back a response body, even thought that's not a problem with my use case.