Overall Satisfaction with Zapier
In my department, we need to send information from our workflow to a Google Drive folder, and we do it through Zapier. It was easy to set up and solved a really complex problem if we were to use web services or other integration mechanisms.
The business case is that we have an approval workflow, including several attachments, and when it is approved, we want to store all of them in a shared folder. The same business case could apply to send information when the workflow goes to a spreadsheet in Google Drive (via Zapier).
The business case is that we have an approval workflow, including several attachments, and when it is approved, we want to store all of them in a shared folder. The same business case could apply to send information when the workflow goes to a spreadsheet in Google Drive (via Zapier).
- Easy of use to set up the connection
- Stability - it has been working for a while
- Reports when anything unpredictable happens
- 100% cloud, no hidden surprises
- Language support. I find it difficult to manage both languages at the same time.
- Not too simple to log errors for improvement.
- We solve a problem that would have costs thousands if custom developed, with a few clicks and a couple of hours.
- We are able to improve (modify) the whole integration without coding (developer hours, testing, deploying...).
We didn't evaluate any other IFTTT tools. Having said that, we know there are some competitors. Even Microsoft I think has an IFTTT tool similar to Zapier. Of course, Web Services, SOAP or REST are an alternative to Zapier, even competitors, but they require coding are much more complicated and expensive to deploy.