Since Zapier is a tool, it does not need a deployment. It's a tool that can be created in two minutes.

We did the implementation of Zapier in-house. 

I do the maintenance of the solution and the maintenance is similar to any other RPA. You don't touch it until there's a problem or you need to do some adjustments to it. If there's a problem, then you figure out what the problem is and then you fix it, and then you don't touch it again until there's a new improvement to do. That's the beauty of it.

The implementation can be easy if you start with simple scenarios.

Then, if you plan on implementing more refined multi-steps zaps, it can become useful to get some support.

Also catching the sample data and filed you're looking for can sometimes be a bit long and reduce the momentum of the project.

We did it on our own. I guess vendor's assistance is unnecessary.

I did it in-house. In fact, I did it myself.

We consulted a third party to implement this solution. 

We are a small organization with about four or five people working with Zapier. We are the integrators, and we also do a few other things also that Zapier is not able to do. We address some of those gaps in our own implementation.