Summary This blog highlights how Azure Logic Apps was used to overcome a critical API limitation encountered during the integration of Zoho People with FNO for payroll management. During the implementation for a global manufacturing hardware enterprise, we discovered that Zoho’s API allows a maximum of 200 records to be fetched in a single request. While this limitation may not impact smaller organizations, it creates significant challenges for enterprises managing large employee datasets. To address this issue, a scalable Azure Logic Apps solution was developed that dynamically retrieves records in batches, consolidates the results, and returns a complete dataset for downstream processing. This blog explains: Table of Contents 1. Customer Scenario During the implementation of a payroll integration between Zoho People and FNO, employee master data needed to be synchronized automatically to support payroll processing. The organization maintained a large workforce within Zoho People, and payroll operations depended on accurate employee data being transferred to downstream systems. As the integration design progressed, a significant limitation was identified within Zoho’s API framework. The API could return a maximum of 200 records per request. For organizations with hundreds or thousands of employees, this restriction created a challenge in retrieving complete employee datasets efficiently. 2. Business Challenge The integration required access to the full employee dataset from Zoho People. However, the following challenges emerged: Limited API Response Size Zoho’s API only returns 200 records per request. Large Employee Dataset The organization maintained significantly more than 200 employee records. Manual Pagination Not Feasible Static API calls would require manual intervention or complex custom development. Scalability Concerns As employee counts continued to grow, the solution needed to support future expansion without requiring redesign. The objective was to create a scalable and automated mechanism capable of retrieving all employee records regardless of volume. 3. Integration Architecture The solution architecture follows a simple but highly scalable pattern. Process Flow 4. Configuration Steps Step 1: Add HTTP Trigger Step 2: Initialize Variables Step 3: Do Until Loop Step 4: HTTP Request Action Step 5: Output Variable Step 6: Compose Variable Step 7: Append to Array Variable Step 8: Set Variable Step 8: Increment Variable Step 9: Add Response Trigger 5. Why Azure Logic Apps? Azure Logic Apps was instrumental in creating a flexible and efficient solution. Key capabilities that made Logic Apps the ideal choice included: Dynamic Variable Management Allows runtime manipulation of counters and arrays. Scalable Workflow Execution Supports large datasets without requiring custom application development. Native API Integration Provides seamless connectivity with REST-based services. Low-Code Development Accelerates implementation and simplifies maintenance. Enterprise Reliability Offers monitoring, logging, and error-handling capabilities required for production environments. 6. Outcome The final solution successfully overcame Zoho’s API record limitation. The Logic App automatically: This approach ensured the success of the Zoho-FNO integration while maintaining scalability for future business growth. 7. Business Impact 1] Fully Automated Data Retrieval Employee data is retrieved without manual intervention. 2] Improved Scalability The solution can support organizations with thousands of employee records. 3] Reduced Development Complexity Logic Apps eliminated the need for extensive custom coding. 4] Faster Integration Processing Data retrieval occurs efficiently through automated pagination. 5] Improved Reliability Built-in monitoring and error handling improve operational stability. 6] Future-Proof Architecture The solution continues to perform effectively as employee counts grow. To conclude, Integration projects often reveal platform-specific limitations that require creative problem-solving. In this implementation, Zoho’s 200-record API limitation had the potential to impact payroll synchronization for a growing workforce. By leveraging Azure Logic Apps, we developed a scalable and automated solution capable of dynamically retrieving and consolidating employee data regardless of record volume. The solution not only resolved the immediate challenge but also established a reliable and future-ready integration framework capable of supporting continued organizational growth. For organizations facing similar API limitations, Azure Logic Apps provides a powerful platform for building scalable, low-code integration solutions that simplify complex data processing requirements.

Integration platforms are critical to modern business operations, allowing different applications, data, and systems to communicate effectively. While both serve the purpose of integration, they cater to different needs and scenarios. In this blog, we’ll compare BizTalk and Azure Logic Apps, helping you choose the right platform for your business. Outline 1. Opening Section: 2. Introduction: 3. Core Content: Key Differences Between BizTalk and Azure Logic Apps: When to Choose BizTalk Server: When to Choose Azure Logic Apps: 4. Conclusion and CTA: In conclusion, BizTalk Server and Azure Logic Apps cater to different integration needs. While BizTalk excels in enterprise-grade, on-premises scenarios, Azure Logic Apps shines in cloud-native, modern workflows. Choosing the right platform depends on your organization’s integration requirements, scalability goals, and budget. CTA: If you’re still unsure which platform aligns best with your needs, our team of integration experts can help. Contact us for a detailed assessment and tailored recommendations for your business integration journey. Let’s streamline your operations and drive growth together

Introduction Integrating Salesforce with InforLN is a critical task for organizations looking to streamline their sales and billing processes. With the AIS Interface, businesses can efficiently manage data flow between these two platforms, reducing manual effort, enhancing visibility, and improving overall organizational performance. In this Blog, it shows the detailed information for integration between Salesforce to InforLN. The AIS Interface is intended to Extract, Transform and Route the data from Salesforce to InforLN. The steps for integration would be same for different entities. Many organizations need Salesforce to InforLN integration because of the below reasons: Event Scenario Pre-Requisites: Process Steps: On Demand Load Scenario Pre-Requisites: Process Steps: Conclusion Based on the above Integration scenarios Azure Developer can easily navigate for the integration implementation and they can choose between Event Driven or On-Demand based on the business requirement. This integration not only simplifies complex processes but also eliminates redundant tasks, allowing teams to focus on more strategic initiatives. Whether your organization requires event-driven or on-demand integration, this guide equips you with the knowledge to implement a solution that enhances efficiency and supports your business goals. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

High-level steps to start building B2B logic app workflows: Creating a Key Vault for Certificate and Private Key Create an Azure Key vault. In the next step, Select Vault access policy and select the Users. Select Review + Create. Add the access policy and assign it to Azure Logic App. Create Certificate Click the Certificate and Download Create a Key and attach the .pfx format file. Creating two Integration Account for adding Partners, Agreements and Certificates Create 2 integration accounts, one for sender and one for receiver. Add the Sender and Receiver Partners in both the integration accounts. Add a public certificate in sender integration account and a private certificate in receiver integration account. Now we need to add the agreement in both sender and receiver integration account. Sender Agreement Send Settings Receiver Agreement Receive Settings Creating two Logic Apps, one for Sending (Encoded Message) and one for Receiving (Decoded Message) Create two logic apps and add the integration account in respective logic apps. Logic App for Sender (Encoding Message) Logic App for Receiver (Decoding Message)

In this Blog, it shows the detailed information for integration between SAP B1 to Salesforce. The AIS Interface is intended to Extract, Transform and Route the data from SAPB1 to Salesforce. The steps for integration would be same for different entities. Event Scenario Pre-Requisites: Process Steps: On Demand Load Scenario Pre-Requisites: Process Steps Based on the above Integration scenarios Azure Developer can easily navigate for the integration implementation and they can choose between Event Driven or On-Demand based on the business requirement. We are just getting started with Azure Integration Services and stay tuned for more in this series.

If you earlier have exported a Logic app template for further use and deleted that logic app, then below are the steps to import an already existing Logic app template as a Logic app. Go to https://portal.azure.com and then to the Logic app. Open any Logic app. For example, I took the below logic app. Go to Export Template. Click on Deploy Click on Edit Template Click on Load File. Select the template you want to import. Change the name to whatever you want. Here I will keep it as it is and Copy the name for further use. Copy the Name and click on Save. Check this page if it’s the same name and resource group as desired. Click on Review and Create. And then again, click on Create to create the Logic app. Now the Logic app template is imported and ready to use. I hope this was helpful.

Login to https://portal.azure.com/ Search for logic app in search bar in top header. Click on Add. After clicking on Add, a new form opens. Select Subscription, here I selected Pay-As-You-Go. Select Resource group, here I created new Resource group with name AzureLogicAppLearning. Enter Logic App name in my case it is SendEmailOnAccountCreation. Select the location, here I selected Southeast Asia. Now, click Review + Create. After, clicking Create Deployment of app starts. Post deployment completion you will be redirected to App overview page.

Read this blog to understand how one can create logic App using Azure portal to create an API for SQL DB.