I am a software developer, have a paid professional plan, and am almost out of my "zaps".
Here are a two of my favorites:
* Non profit community organization wants to sell event tickets. Paypal Order -> Add row to spreadsheet for simple reporting -> Add/Update user in mailchimp with a tag so they don't get future emails asking to buy tickets again.
* Small client wants a gated webinar signup. Wordpress Contact Form -> Zapier Endpoint POST -> Add user to Zoom Registration -> Add/Update to mailchimp with a source tag -> Add row in spreadsheet
Could these be done without zapier? Sure. But using zapier we can create that within 30 minutes without a server, or even dealing with serverless. Even if someone had those workflows as a one click install for lambda workflow, I would rather use zapier than deal with any AWS overhead.
To everyone who thinks that "a webform to google docs" is the most common use case you are probably right. If you think that you could create the infrastructure to do that consistently with automatic retries, logging, error handling, keep on top of API changes from both ends, across dozens of clients, proper authorization and secret management, for cheaper than $50/month, then you are kidding yourself.
Here are a two of my favorites:
* Non profit community organization wants to sell event tickets. Paypal Order -> Add row to spreadsheet for simple reporting -> Add/Update user in mailchimp with a tag so they don't get future emails asking to buy tickets again.
* Small client wants a gated webinar signup. Wordpress Contact Form -> Zapier Endpoint POST -> Add user to Zoom Registration -> Add/Update to mailchimp with a source tag -> Add row in spreadsheet
Could these be done without zapier? Sure. But using zapier we can create that within 30 minutes without a server, or even dealing with serverless. Even if someone had those workflows as a one click install for lambda workflow, I would rather use zapier than deal with any AWS overhead.
To everyone who thinks that "a webform to google docs" is the most common use case you are probably right. If you think that you could create the infrastructure to do that consistently with automatic retries, logging, error handling, keep on top of API changes from both ends, across dozens of clients, proper authorization and secret management, for cheaper than $50/month, then you are kidding yourself.