Integration Use Cases for integrator.io
Celigo is pleased to announce the Free Edition of integrator.io iPaaS integration platform. You can test-drive the integration middleware to experience the benefits of an easy-to-use, powerful, out-of-the-box integration solution for free.
The Free Edition comes with the ability to have one active integration flow using most features of integrator.io, including the ability to create either simple and complex integration flows. This article describes example integrations that you can use with your Free Edition or any other integrator.io plans.
What is an Integration Flow?
Integrator.io enables the automatic exchange of data between applications by using integration flows. When creating an integration, a step-by-step wizard guides you in specifying the data that will be transferred (e.g., imported) from an application or file, and the destination application or file to where that data will go (e.g., export).
Integrator.io supports integration flows between two cloud applications in a point-to-point integration in addition to complex integration flows for data from multiple applications to be transformed and routed to multiple destination applications via orchestration.
Example Integration Flow: New Customer Updates
Automatically ensure new customer information is available across all relevant applications. Whenever a new customer is created or updated in a front-office application, such as e-commerce storefront or CRM, new customers are automatically created or updated in a back-office application, such as accounting or ERP.
Whenever a new shopper creates an account in Magento or Shopify, a new customer record is created in NetSuite or QuickBooks. If you wanted new records created only if an order is placed, you can specify this condition as part of the integration. You will have the ability to specify the time intervals when these updates are done — from every 15 minutes, specific days of the week, or other intervals.
Example Integration Flow: POS Payments
Companies using point-of-sales (POS) systems to capture sales can automatically make sure POS transactions are available across all related applications. For example, whenever a new sales transaction is processed by a POS, a new sales order is automatically created in the relevant financial application.
Whenever a new sales transaction is authorized in Braintree or Square, a new sales order is created in FreshBooks or NetSuite. The sales order is marked as paid cash transaction. Reference ID’s can be associated with these orders in NetSuite, such as store number, along with identification of them as POS orders.
Example Integration Flow: Order Status
For prompt customer service, especially during busy holiday or shopping seasons, up-to-date order status and tracking information can be made available in a customer service application to help support reps quickly respond to customer inquiries. Order statuses from fulfillment or e-commerce applications, such as Amazon FBA and Shopify, are made available within a customer support application, such as Freshdesk and Zendesk.
A variation on this flow can be to make refund statuses available in the customer support application. Typically this would require an integration flow between a financial application, such as NetSuite, and customer support application.
Example Integration Flow: Weekly Reports
Weekly or monthly reports of data from multiple database tables can be set up using an integration flow. For example, an integration flow can join data from the customer and the sales database tables. The data can be converted into an XML or CSV file which is then sent to a FTP server or another cloud application on a weekly or monthly schedule.
Your Monthly Competitive Advantage
Access integration-driven automation tips and resources in the Celigo Automator newsletter.