Unlocking Efficiency: How to Create a Reusable Generic Logic App for Multiple Projects

This article describes how to create a generic logic app that can be reused for different project requirements.

A basic question first….Why would you want to create a generic logic app?

Well, using or reusing a generic logic app makes sense if a team of Data Engineers recognizes a similar or near-similar suite of use cases. The logic app, in this situation, can be heavily parameterized to cater to different conditions.

Before I proceed to show how to design a generic logic app, below is the list of advantages and disadvantages so you can decide if you and/or your team would benefit from it.

Advantages

1. Multiple team members can reuse the logic app for different projects.
2. Easier maintenance since the team as a whole works to maintain one logic app as opposed to a wide variety of logic apps.
3. One place to debug a pipeline failure instead of debugging multiple logic apps for multiple projects.

Disadvantages

1. If any of the project’s requirements deviates in the future, that project’s dataset(s) may not be compatible with the generic logic app.
2. If any error arises for any reason in the generic logic app (for ex: connection failure, credentials expiration…