Ability to Archive Integrations

It would be nice if we could archive a complete integration along with any associated flows and connections so it is not displayed on the integrations page. We have a business case where we created an integration that is no longer being used, but would like to retain for future use without having to delete it and recreate the entire integration.

Hi @brandmusclenetsuitec!
Thanks for letting us know! Our awesome support agent, Dan Claypool, recommends that you download an archive of your integration (the integration.zip file), then delete your currently unused flows and integration tiles. In the future, if you need the integration again, you can install your integration.zip as a template. During this process, you can either choose to use existing connections to whatever endpoints are in place, or you can create new ones. Would this work for you? Or are you wanting to continue to be able to view the integration information at any time?

I agree with this - it would be great to be able to mark a tile as archived without having to actually delete it, and then be able to view all archived tiles and "un-archive" any as needed. Basically just being able to hide unused tiles or flows so that they don't clutter up the active integrations that we actually need to monitor on a daily basis. The same thing could be accomplished by allowing "folders" for integration tiles.

Hi @sarissasanderson, we have a similar feature within an integration tile that allows users to organize their flows within groups. Here is an article with more info on how to do that.

Hey Kevin, that is awesome for flows within a tile but what about organizing the tiles themselves?

How were you looking to have your tiles organized? Depending on your business, there's a couple ways to have them set up. For example, one tile could represent Company A and another Company B. Each tile could have flows organized in groups by different business processes (HR integrations, CRM integrations, etc) or different applications.

Another example could be having a tile dedicated to different departments within the business and keeping the flows separated that way.

Example:

We basically have about a dozen integration apps or groups of flows that are already organized into their own tiles. About half of those we are not using at the moment - like for marketplaces or stores that are out of commission right now, or for older integrations that we still reference sometimes for mappings or historical information. We don't want to delete them, we just want to hide them from our standard view on login.

@sarissasanderson I've passed on your request to the PM team for consideration. Thanks a lot!
You're also welcome to provide your ideas on the Product portal!