Integration platforms such as Zapier and IFTTT allow users to create custom flows that link events taking place in one application to an action that should occur in another. With the help of these platforms, people are able to automate work that would have otherwise required manual input. Thanks to this, the mundane tasks of everyday life can be delegated to computers while people are allowed to be more productive with their time. The question is, how exactly does Zapier and IFTTT implement these integration solutions, and how do they compare? From the perspective of a company that seeks to publish their application to the catalogues of these platforms, one would be interested in knowing what specific problems these platforms can solve, how they are solved, and how the solution can be evaluated. One theoretical framework that can be applied in order to answer all of these questions is known as enterprise integration. The problem is that an analysis of Zapier and IFTTT through the context of enterprise integration does not exist. The purpose of this thesis was to create this analysis. By doing so, companies would be able to make more informed decisions as to the selection and use of these technologies. Action research methodology was used to gather qualitative, inductive data, through the implementation of five smaller scale projects. Each of the projects was an investigation into a common type of problem that enterprise integration is typically used to solve. For each project, a set of criteria that were also taken from enterprise integration were used in order to evaluate the implementation’s strengths and weaknesses. A statement as to which of these platforms is better than the other was not found. However, similarities and differences between the two were able to be determined. The results indicated that Zapier’s strengths came mostly from the fact that it offers developers more freedom than IFTTT does, but that IFTTT had strengths that came from its ability to offer reliable delivery without compromise, and that it allowed developers to create better solutions in multiple scenarios. Findings like these were found and expressed through enterprise integration. / Integrationsplattformar såsom Zapier och IFTTT låter användare skapa sina egna skräddarsydda flöden som sammankopplar händelser som uppstår i en applikation till en aktion som ska ta plats i en annan. Med hjälp av dessa plattformar så kan folk automatisera arbete som annars hade krävt manuellt input. Tack vare detta så kan banala vardagsaktiviteter delegeras till datorer medan folk tillåts att vara mer produktiva med sin tid. Frågan är, hur exakt är Zapier och IFTTT:s lösningar implementerade, och hur jämförs dem med varandra? Från ett företags perspektiv som vill publicera sin applikation till dessa plattformars kataloger så skulle man vara intresserad av att veta vilka specifika problem dessa plattformar kan lösa, hur dem kan lösas, och hur lösningen kan utvärderas. Ett teoretiskt ramverk som kan appliceras för att svara på alla dessa frågor är enterprise integration. Problemet är att en analys av Zapier och IFTTT från kontexten av enterprise integration inte existerar. Syftet med denna uppsats var därför att skapa denna analys. Genom att göra detta så kan företag ta mer informerade beslut med avseende på hur de väljer och använder sig utav dessa teknologier. Aktionsforskning användes för att hämta kvalitativ, induktiv data, genom implementeringen utav fem mindre projekt. Varje projekt var en undersökning av ett typiskt problem som enterprise integration typiskt används till för att lösa. För varje projekt användes en uppsättning av kriterium som även dessa var tagna ur enterprise integration, för att bedöma implementeringens styrkor och svagheter. En slutsats om vilket av dessa plattformar som är bättre än det andra drogs inte. Likheter och skillnader kunde dock bestämmas. Resultaten indikerade att Zapiers styrkor mestadels kom från det faktum att dem ger utvecklare mer frihet än vad IFTTT gör, men att IFTTT hade styrkor som kom från det faktum att dem kunde erbjuda garanterad leverans utan kompromisser, och att utvecklare kunde skapa bättre lösningar i flera scenarion. Upptäckter som dessa kunde hittas och uttryckas genom enterprise integration.

This Master's Thesis focuses on integration of software that are provided as services (SaaS) into current on-premise information systems of enterprises. In enterprise computing, services such as SaaS are usually integrated into cloud services. In recent years, cloud services have been experiencing a dynamic growth, and, in various forms, they have been entering enterprises of different sizes and fields. At the same time, the experience show that implementation of SaaS into enterprise computing faces many challenges due to the fact that the SaaS vendors have exclusively focused on improvement of software functionality and the integration itself has completely remained out of their attention. Given that, the integration of SaaS is rather complicated or even inaccessible for many enterprises. In particular, small and medium-sized businesses are a very specific target groups and the traditional integration platforms are unaffordable for them. The goal of this thesis is to develop a methodology based on MeFIS that would cover integration of SaaS into on-premise-based information systems in small and medium enterprises. In this thesis, first, I will define the terms used in integration of IT and cloud services and describe the essential principles, tools, and technologies used. Second, I will conduct a literature review of available sources to find the best methodology for integration of SaaS, which would take into account the specific needs of small and medium enterprises. Third, I will develop a methodology based on the methodology framework MeFIS (Methodology Framework for IS/ICT Systems). At the final stage, the developed methodology will be applied in one company in the Czech Republic. The emerged integration challenges will be described and their solutions will be developed; thus, this thesis might also serve as a specific example of SaaS integration into enterprise information systems within small and medium-sized businesses.