It is mostly focused on integration points, either integrating with CRM systems or Microsoft legacy systems, mainly working with APIs and REST APIs. One use case I worked on for a customer involved integration with Close CRM. This is an open CRM system where I had to retrieve data such as contacts, opportunity details, lead details, and addresses. After connecting with Zapier, the data was displayed in another system using the Zapier app, which is called Zap, along with webhooks for integration.

There was a specific case where data needed to be passed from Close CRM to our custom application. Since we were unable to connect directly from our custom application to Close CRM, we utilized Zapier workflows. Through this integration, we were able to populate data from Close CRM and display it in our system for reporting purposes.

The solution is time efficient and has saved considerable development effort. Tasks that would typically take more than three months were completed in approximately a week.

This has helped us eliminate manual interaction for scheduling tasks and sending notifications. Through these features, we can achieve automation without the need for manual integration.

Creating integration points through webhooks is particularly useful for anyone working on integration projects. There are several built-in features in Zapier for webhooks that can be used effectively.

I have worked with different low-code, no-code solutions, including Decisions, a US-based company, and OutSystems. The solution is quite user-friendly and accessible to everyone.

I have utilized various webhooks available through Zapier for different integration purposes.

Improvement is needed on the user interface aspect. To make it a complete BPM solution, the UI component needs significant enhancement. When comparing to OutSystems, which has better UI capabilities for creating screens and forms, Zapier has basic features for creating pages, screens, and forms, but additional development is needed in this area.

Another area for improvement would be providing more capability to create custom integration points. While Zapier already has more than 2,000 webhooks, users or developers should have the flexibility to create additional custom connectors.

My interaction was brief, consisting of one or two support tickets. The experience was positive with prompt responses from their team.

The return on investment is significant. In a scenario where employing three resources for three months might cost approximately $18,000 to $20,000, Zapier provides substantial cost savings.

The pricing is in accordance with market standards and even lower in some cases. The license setup cost is reasonable.

The sign-up process is straightforward. Users can sign up with their work email, and an organization account is provided, enabling them to start creating workflows and screens immediately.

Based on my experience with cloud integration using Zapier, it is a very good solution. I would rate this solution 8 out of 10.

For multi-step scenarios, I needed to connect multiple CRMs simultaneously within visualization tools, primarily Power BI. I created a workflow connecting Zoho CRM to HubSpot and another platform called Clay for data orchestration and transformation. I pulled the data, created automation through Zapier, connected it with Clay, and once the data landed within Clay, transformed it before connecting Clay with Power BI. I used Zapier again to create automation workflows and provided conditional logic based on user experience and behavioral aspects. When working with campaign data, I specified steps based on demographics, religion, and other requirements. I created those steps and pushed the data through Zapier within Power BI.

It is very helpful, specifically for data professionals because I have exposure to that domain, CRM users, and my colleagues in web development who use it for integration. They suggested it to me, and that is how I learned about what kind of tool it is. It has proven to be quite useful.

Zapier is user-friendly and most information is available within the page for specific automation. When creating data pushes from one source to another through Zapier, or integrating different platforms, everything is clear. The steps to perform, sources, destinations, triggers, and other aspects are straightforward to use.

The automation capabilities are impressive. Zapier is integrated with most applications I have been using, making it helpful for integration within any platform. When there is no custom configuration or integration available between two applications, Zapier provides a solution. There are no limitations with data, particularly in the data analytics and BI dashboard domains. When fetching data through XML, custom coding isn't necessary - configuration and mapping of accounts, columns, and tables between sources is sufficient before hitting the trigger button.

The automation capabilities eliminate the need for manual data retrieval or analysis from different sources. When data is needed, triggering and creating automation pulls data from the source into Power BI or Cognos. By specifying conditional logic rather than transforming and performing conditions within the visualization tool, Zapier provides conditional logic on the behavioral side to get specific data and load it into Power BI visualization tool.

There could be improvements in creating more complex workflows within the data domain. Having flexibility in creating more complex automation would eliminate the need to transform data within the source or destination. Specific workflows could be created to pull transformed data through Zapier workflow directly into visualization tools for dashboard and report creation.

Response time was good but had slight delays when asking detailed questions. This might have been due to the time needed to find exact information through documentation, which could be improved.

I would rate it seven and a half or eight out of ten.

I would rate the customer service as seven out of ten.

We previously used in-house solutions. With multiple CRMs requiring data collection, it was suggested internally that rather than integrating different platforms with different applications, we could use a third-party integrator such as Zapier. By subscribing to that module, it became easier to create workflows and push data from source to destination.

I have used ZoomInfo as another solution, specifically for data integration on the Clay side. I have mostly been using custom, native integration platforms to connect CRM applications to each other. However, I primarily use Zapier for these purposes.

The solution is mostly deployed in the cloud as per requirements.

I have been defining data specifications including data range parameters and specific tables to push for different departments. For example, when working with billing excellence in the finance department or customer value management, I implement conditional logic. For each record, I might require only hundreds of rows with matching conditions, similar to if-else conditions. The same approach applies to date ranges and filtering blank entries.

When I encountered an issue finding a solution, I reached out to the support team who provided excellent assistance with documentation and custom workarounds.

As a consulting firm, we provide services to different clients across Gulf, America, European, and South African regions. We use Zapier for our customers based on their requirements and internally within our company. We suggest it to clients who have large amounts of data, multiple sources, or want to create more automation, including AI or LLM module implementation.

The implementation was straightforward, requiring only specific module definition, source and destination configuration, with comprehensive information available on screen for understanding steps and implementation.

Overall rating: 7 out of 10.

Currently, we are a software company called KlickTipp, and we built a connector in Zapier for our application to access the API. We use Zapier to implement templates for customers, making it easier for them to integrate with our tool. We cannot build a native integration to all tools such as JotForm or Typeform, so we consult our customers to use applications such as Zapier, Make, and n8n. Zapier is the tool with the most connectors and has been quite forward in that case.

In our business processes, we worked with it, but we are switching now because the use cases were connecting our help desk to our product planning tool and then to our development project management tool, from Helpscout to Productboard and from Productboard to Jira.

I have employed multi-step automation workflows in my tasks, taking data directly to Productboard to plan new ideas and insights, and doing some aggregation.

From my perspective, Zapier is a tool that has the most connectors. They have approximately 7,000 connections. That is the most important feature for Zapier, and that is why they are where they are currently in the market.

When working with Zapier, it is easier for customers to use because it has a clear structure compared to Make and N8N, which have a more free structure. With Zapier, there is no need to deal with technical JSON characters. You can start from scratch without paying anything, which is great, but Zapier can get quite expensive fast.

You can build similar or dependent automations in one Zap, which helps with understanding the process without switching between different records.

I would appreciate quicker response times and more direct interactions. It would be great to have a direct contact person for support, but bigger companies usually have solution partners handling support. I do not have a solution partner for Zapier due to using it for small use cases.

I have been working with Jira, Confluence, Workato, Make and n8n within the last 12 months, as we discussed initially.

In my current company, we had significant challenges with Zapier regarding maintenance, as Zaps were often broken, not necessarily due to Zapier, but due to changes in the input variables. I would rate Zapier a seven for stability.

I always consider pricing when thinking about scalability. Scaling it gets quite expensive, and while I cannot evaluate it purely from a technology perspective, compared to Workato, I would give Zapier a seven for scalability.

I have interacted with Zapier's technical support, which was good support, but it was not especially open.

In my earlier company, we initially just worked with Jira automations for the Atlassian tool stack, but then we realized we needed more complex integrations and used Workato which is more for enterprise customers because they have many enterprise features.

Zapier was present when I joined my current company, and then we switched to n8n.

Currently, we are a software company called KlickTipp, and we built a connector in Zapier for our application to access the API. We use Zapier to implement templates for customers, making it easier for them to integrate with our tool. We cannot build a native integration to all tools such as JotForm or Typeform, so we consult our customers to use applications such as Zapier, Make, and n8n.

We currently switch from Zapier because it was so expensive. My experience shows that for our use cases, other tools are cheaper. We use Zapier more for templates where we do not have to pay at all because we are partners with Zapier, and our test account allows us to build templates and test connectors.

They currently do a lot with MCP and AI agents, which is a big topic in integration. I think that is the right way to go. However, pricing is currently the most crucial issue.

I would rate Zapier overall a seven.