On Demand Webinar

Enhance Your SAP Business ByDesign Practice with Celigo’s iPaaS: How to build your first integration flow

The Celigo platform is a complete integration platform as a service that enables you to automate business processes and build integrations across thousands of applications faster and easier than any alternative solution. Celigo provides an intuitive, easy-to-use graphical interface with purpose-built user experiences for business users and developers. AI and embedded business logic enable all users to rapidly create and deploy integrations and package connectors, flows, business logic, and mappings into reusable templates.

With Celigo, you can provide your customers with business process automation solutions and deliver on integration projects faster, with less risk, and at a lower cost.

In this on-demand webinar, Chris Bidleman, Director, Integrations Solutions at Celigo, provides a first look at Celigo’s iPaaS and shows you how to build an ecommerce integration flow for SAP Business ByDesign.

Topics include:

  • An introduction to the Celigo Integration Platform
  • Overview of prebuilt connectors and universal connectors
  • Getting started: How to build your first flow
  • Advanced Capabilities
  • And much more!

Watch now!

Full Webinar Transcript
Hi, everyone. Thank you for joining our webinar today. I’m Laura Dougherty, head of strategic business development here at Celigo, and we have with us today, Chris Bidleman, Director of Solution Integrations. Today’s webinar is about enhancing your SAP business ByDesign practice with Celigo’s iPaaS, and we’re going to show you how to build your first integration flow on our platform. So just a quick overview of Celigo. For those of you who aren’t aware of who we are, we are an iPaaS platform. We have over 4,000 customers around the world today. We are located in San Mateo, California in the United States and have several offices in the US and across the globe as you can see here. So today we have over 480 employees, and we support over 40K active business processes, which is a lot of data that we’re automating every single day. Our customers are very happy with who we are, as you can see here, and what we do. So there’s a lot of great reviews that we have in the industry. We have a lot of mid-market customers. As you can see here, we also have a few enterprise customers as well. We are experts at serving this market. We have a fantastic product that really meets their needs. Mid-market clients have a lot of enterprise company needs as well, but they’re mid-market, so we’re able to come in with an effective, cost-effective platform that can meet their needs and be simpler for them to use so they can integrate really into any platform across their organization. So our mission as Celigo really is to help accelerate the digital transformation, which is exactly what many of our ISA partners like Business ByDesign are doing. And it really helps make the integration simpler for IT and business users across the organization and for our partners who serve them. And our platform itself has lots of different features. Like I was talking about, this is really a very robust solution for the mid-market. We have connectors to– over 250 pre-built connectors to different endpoints. And then within that, we have some pre-built integrations. We’ll show you one of those today for Business ByDesign. We have custom integrations that can be done here. And unlike most of our competitors, we can actually build integration apps that are licensed separately from the platform. And that’s something that we can do. You can do as a partner. That’s a fantastic way to create your own products on our platform. And then at the bottom, talking about security and governance, we have type one and two compliant GDPR, HIPAA. There’s a lot more going on there that we really encrypt everything across the board so that it’s very secure, and that’s important to many clients, given that they have sensitive data that’s going back and forth. Within the middle of this, we have lots of different operations that we can do. So whatever data format the source application is in, we’re able to take that and transform it to whatever it needs to be at the destination endpoint, and within that, we can do custom logic. We can do scripts, JavaScript, everything within there so that you don’t necessarily have to do it at an endpoint. Today, we’re really going to focus on the flow builder and build that first flow. The platform can really help enhance your practice in several ways. We can accelerate time to value so that you can get projects done quicker to meet deadlines, take on more projects, keep customers satisfied. You may be able to reduce maintenance. Celigo basically is going to maintain the APIs that are in the pre-built connectors that you don’t have to. That can be very cost-effective. Nobody likes doing that job. it’s tough. We have a huge team that that’s all they do as part of their jobs. And on top of that, we can also maintain the integration flows for you or your clients as needed. We also help you meet requirements that your customers have without adding complexity to deals and what that means is that you can really– we don’t impede the process, the sales process. You can really keep moving that along because we give our price points affordability when it comes to our subscriptions. Plus, the platform is dynamic and it can adapt to new needs and requirements so that you can continue to satisfy clients over time. They have free training and certification that you can get from us. You don’t have to pay anything to be part of programs. And in addition, we have a lot of in-house business process expertise and I think this is probably key where you can really leverage your relationship with Celigo. We know these processes because we’ve done thousands of ERP integrations for our clients, our customers and we can really share our knowledge of best practices when needed. And in addition, because of our relationships with ISP partners, we’re able to leverage our– those relationships to help with these integrations. So it’s a very strong partnership we need to lean on as for business process information. So regarding business processes, today we have the order to cash API built-in and those include here are the item inventory, customers, outbound delivery. Everything you see here is already pre-built and we manage that within our connector. We’ll be adding many more business processes to the connector shortly. So you’ll see here these are the common use cases for e-com order to cash with e-commerce marketplaces shipping and fulfillment. And what you see here, we actually have connectors for all of these and many more. This is a very limited amount – Chris will show you shortly here – of the APIs that we have for order to cash business processes. And what’s great about Celigo is if there’s an API connector not here that’s– that might be on a roadmap or it might be something if it’s an in-demand it’s something that we can add to our roadmap. So we always want to hear your feedback as to what would be helpful for you and your customers. Today’s demo we’re really going to phone in on building a sales order flow from SAP– from Shopify to SAP business supply design so you can see what it’s like to build a sales order flow for the order to cash business process. And from here, I’m going to hand over to Chris Bidleman to show you how to build an integration flow. Thank you, Laura, and good to be with you. As Laura said, I’m the director of solution integrations at Celigo and today I’m going to be kind of taking a deep dive into our Integrator.io platform, which as Laura mentioned, is our iPaaS, integration platform as a service. We do live in the cloud. We’re part of the Amazon AWS infrastructure is where it lives so it does provide four-nines of reliability within that environment. And so you’ll be comfortable knowing that it’s going to be up and running and you can depend on it. So what I thought I’d do is just give you sort of a tour of Integrator.io and then also be able to do a bit of a dive into actually building one of the SAP business by design flows. On the left is some of your tools that are available within the platform itself. We provide a lot of different ways to be able to move data. Today, we’ll be focusing on the flow builder but we also provide other ways to be able to import and export– or import data through their data loaders, their CSV imports, and different reports that are available within the platform itself on error reporting and other things. And also so a developers playground, which is a lot of our tools and connectors that you can– and handlebars that you can actually play with. Try a different scripting and other things to be able to see what the results are going to be. So again, it gives you a lot of just sort of things in your toolbox as far as resources that are available within a data flow. Let me kind of break down a little bit. So things are through connection, which I’ll show you how we set up a connection and what our by-design connector looks like. We have imports, which is any data moving in or importing into an application, and then the exports is data flowing out of that particular application. So we’ll show that within the flow builder how that all works. We do provide some additional scripting capabilities within the platform. So the way the Integrator.io works is we convert everything to JSON. So no matter whatever the endpoint language it’s talking, be it a database, if it’s a restive, if it’s EDI flat files. We actually convert everything to JSON, then that allows us to be able to do different type of Java scripting manipulation of that data, if necessary, for certain business rules if you want to do some data transformations from one system to another that provides you some things, so I’ll show a little bit about that. And then we also have some on Prem agents that can also be installed. So if you have a database on Prem, SQL, any these other common SQL databases, we have some agents that can also help with that connection. And there’s a lot of other things that probably pertain to this. As Laura mentioned, we also have a lot of help available to be able to do self-service. So a very extensive help center that we’re able to show you and walk you through how to get started about the connectors. We have office hours that you’re able to use to be able to ask questions, and we’re providing a series of live training sessions to be able to again hone your skills and other information. So just entering in any different terms that you might have as part Integrator.io. I want to learn about– be able to put our handlebars, a lot of information is available that is contributed by many, many folks within Sligo and in our community. And then what’s also available as part of a contract, you have to have support tickets that you’re able to reach out Sligo and have first and second line support available to you. And as Lawrence mentioned, we also have Sligo University, which is a very robust online library of video certifications that you can go through and learn how to use Integrator.io. I’ll encourage anyone who’s actually going to go in here to get at least what we call level two. We have up to four levels and I understand they’re going up to level five here pretty soon. As far as just enhancing your skill sets associated with the Integrator.io and be able to use it effectively. Then finally, let me jump into the marketplace too, because this is where a lot of the– as Laura mentioned, we have different templates that are available. So these are pre-configured templates. We have integration apps which are also think of it like a plug-in that already has a lot of the applications and the flows are set up for you. But in our case, we have templates available for a lot of the ecosystems that we’re talking about. So we’ll do ByDesign, you can see what different data flows are here. And in Shopify, we’ve been doing Shopify for a long, long time, and you can see the different connections that we have and templates that we have available to that. So let me show you. Let me go ahead and collapse this to give me a little bit more room. So for you, if you’re going to start out in doing a Shopify integration, we have these templates. And again, this is what’s in the marketplace. We have these four use cases that are available, and I’ll show you these coming up here. And it does describe a little bit about what each one does. Within the readme is also fairly robust description of all the different steps that you need to do. So any IO template does have different types of instructions about the steps you need to go through to be able to install it properly, configure it, because the IO template is not a plug-and-play. In our world, there is really no such thing as plug-and-play. Everyone’s system is going to be different, how they used it, how they configured it, what custom objects they may have in their fields. And so it’s important to be able to at least have a good starting point. And then that’s what this does. So for us, you can install the templates. It will step you through sort of a wizard as far as setting up the connections to each of this business systems and do the install into your environment. But I’m going to skip that step and just kind of jump back to hopefully where I was with the different things. So once you do the install, the four different applications are, or excuse me, data flows are installed for you. They will be off, so they’re not going to start running on you at that time. So let me kind of go into a little bit about what the flows look like. So this is what we call as far as our flow builder that Laura mentioned. On the left here you’ll see sources. This is where the application is getting its information from. And then destination as I talked about, this is the export and these are the imports and the different steps we’re going to go into. And we do have an SAP business ByDesign connector. So let me show you a little bit more about that particular thing. I’m actually going to create a flow. Brand new flow. This is ByDesign, excuse me, ByDesign. I can’t type. Demo, you can name it whatever you want, and I’m going to take a source. And as Laura mentioned, we have a large library of several hundred different connectors, pre-built connectors that allow you to do connections to databases. We have our universal connectors. So for example, our business ByDesign connector is using OData for its business objects. Then I’ll show you that here in a second. But if you want to do SOAP API connections to ByDesign, then this is where you would create that connection to that service and then be able to build out that. So there are cases where it might make more sense to do the SOAP API calls into ByDesign as opposed to using this OData connector. And then there’s a large library of other common things that we do, like big commerce is another one. We do a lot of connections to Salesforce. We get asked about Magento. So again, we have a lot of connectors to all those different business systems, as well as backend systems and the different databases that are supported. but for us, I’m going to go for this Business ByDesign, and I’m going to use an existing connection that I already have set up. And the way you would normally do this is, you may have two different connections. One would be to your production tenant, and then you would also have a sandbox tenant to be able to connect to. So you’d just be able to pick the different connections that you would want for that. So for this export, as I mentioned, we have the ordered cash objects, business objects that are available to you. We’re going to be able to do a get in a different type of thing. So in this case, you can see we have outbound deliveries, inbound deliveries, sales orders and such, that we can do different queries. And then once you pick that particular operation, then you have a choice as far as getting different operations that you might want to do. In this case, I want to get sales orders, and we have different export types. I will get all the data. I can do deltas based on last-modified date, so we’ll filter out everything that was created since the last time the data flow ran, and you’re able to be able to see that. And you can also launch different parameters. And within this view, we’re also able to preview some of the data. So if I do a call out, this actually is calling ByDesign. You’ll see the JSON that is created from that, and all the elements that are available to you to be able to map to, and you can kind of see the data here. So again, this gives you a nice view into what is going on behind the scenes once you actually connect to that application. So on the import side, so if I was actually going to import something into ByDesign, let me show the business objects associated with that. Let’s see. I’m going to import into the destination. You can also see, I could do lookups. So there are cases where you may want to look up a particular entity’s values, items, or the customer or contact information. There’s maybe some information you need from that record that you need to pull, prior to being able to do an import. So that’s where you would do a lookup. But in this case, I’m actually pushing or importing data into the ByDesign system. And for this import, I’ll just name it, again, we have the different business objects that are available to you. So in this case, we push in based on the other side of things, as far as customer and inventory items and supplier invoices that we can set up within that ByDesign, and I’ll get into a little bit more of the detail of what’s actually underneath there. Let me just go ahead and pick one so I can save this. So then I’m going to do items. If I was going to create an item that’s where I would save it. And there you go. And so there’s your first data flow. So we’ll get into the mapping. So let me go look at the orders. And again, this will allow you to be able to see a little bit more what’s going on. So this is the Shopify connector. We’re exporting data out of there. Similar sort of view that we provide to you. It allows you to be able to, again, whatever system you’re connecting to, as far as integrator.io allows you to be able to be familiar with the navigation and how to set things up. In this case, I just set up a particular order. I’m pulling out of Shopify, but very similar sort of thing. We can pull out lists of orders, look for specific orders, order counts. Normally, this would be set to list all your orders and then be able to do a delta change because it’s the same sort of thing. Shopify also provides webhooks, which are a different type of real-time actions that users can subscribe to. So we can set up a listener to be able to– whenever a new order shows up in Shopify, we can actually then have a listener pull that in and then be able to import it in. So you do get virtual real-time integration. But in this case, this is more of a scheduled flow that we can also set up to be able to pull particular orders. And as I mentioned before, the same sort of preview where if I was going to pull this order, this is what it would look like coming out of Shopify, and describes the different nodes that are available for customers and other stuff. But we’ll get into that a little bit here when we start getting into the mappings. Within any exports, as I mentioned, we have a lot of other tools that you can utilize it, you can transform it. So if you want to rename fields or change the data structure, you can do that. We have filters. So maybe status-wise, you only want to look for released orders or any other type of criteria you might want to do to make sure that we’re not getting everything coming through. It’s particularly important if you’re getting a webhook. So it can be fairly chatty. You don’t want to know about every update. You only want to look for updates with a particular status. So that’s how you would do that. And as we mentioned, once you have the JSON data, you can also add on additional business features as far as through JavaScripting, to be able to look for particular values, replace values, restructure data because maybe the way the data looks for one system isn’t compatible with the other system. So you need to maybe change the date format or do some other things. We also have handlebars that also assist with that, which I’ll show in a little bit. But again, very powerful. But for the most part, you should be able to use a lot of the core tools there. But if you really want to get deep into the weeds, there’s a lot of other options. Actually, let me talk a little bit about this business use case. So once you get an order, there’s essentially a couple business objects you need to deal with. You need to first see if that customer exists within ByDesign to either update that customer prior to actually creating the sales order. We’ve also seen cases where somebody doesn’t want to create a a new account for every single customer that they have. Maybe it’s more of a B2B, business-to-business, type of relationship, so it’s the same account. Or you set the account up at the store level by design. And then you map in all the contact and shipped to and billed to. So, often, you won’t even have this bubble here, which would be very simple. Just hit the X, and then away it goes. And you don’t have to use that, and you can just do that. So what we’ve done, you would hard code that account value in there, and so then you wouldn’t necessarily need the step. But, again, it really depends on your business use case that you would have. Now on the by design side, there’s two different views you have. We have the by-design API view, which has the O-data objects, as I mentioned before, from that. But you also are able to do the HTPP view, which actually shows you what the data is looking like, the different HTTP calls. So it’d be a post or a patch. And then the different sections around what do you do for new data, and then what is the call for updating existing data? And so does get into a little bit more detail. So this is how you would do the various mappings. I was going to create a new user. And as you can see, it’s just the very basics as far as the things that you would map. So the way this is set up is here’s my record. This is all the information I have available to me from Shopify. It’s all in JSON. And we’re basically taking the file path to replace that information that was in here. And then this is your code. And then here is a preview of exactly what’s going to be sent to that. So in this case, we can see I’ve actually mapped in the first name, last name. And then if I wanted to just do another action, maybe it’s a person company, want to be able to have that in, the tool also provides an ability to be able to not– you don’t have to go through this. You can actually type ahead and look for something. So if I wanted to see using a double handlebar, you can go in the company and can see all the fields that are available for a company in this case. Okay, I want to use the default customer company name. Of course, I’m actually going to do bad JSON here because if I try and do a preview, we do have an editor that also helps with your syntax, make sure it looks right. Oh, yeah, I forgot to do the double quote there, and so then I can crack that, and then be able to show exactly, “Okay, now I’ve just mapped in the company.” And if they actually had it back there in the company, then it would show up here. But you’ll see it. It did show up in the JSON that’s going to be going forward. So that’s how you would add additional things. But we also provide the ability to be able to do what’re called handlebars. Handlebars, if you’re not familiar, is a JavaScript that allows you to be able to do a lot of different functions. You can add values, replace values, be able to do business logic if then else kind of logic, and be able to do that. So we have a really– we sport a very large library of that. And so you are able to add in a lot of those type of business logics within this JSON here. Adding different fields is actually very simple. In this case, maybe you have a field that you want to combine a couple of different fields, allows you to be able to do very simple. And as you can see now, it’s going to combine those two fields, and now you have the full name within a field. So it provides a lot of power and a very flexible ability to be able to manipulate the data exactly how the import system needs to see it in it and be able to only use the data that you need out of the huge blob, if you will, of data that does come across on some of these different things. All right. I don’t need to save those changes.So that’s the steps as far as the customer. Let me go and just not say those steps. Now, once you create a customer, you’re going to want to be able to capture that ID. What was the new ID for that SAP customer? So we have response mappings that allow you to be able to capture that data because then once you move into the sales order itself, you’re able to utilize that data and then be able to use it within your mappings, create your different buyer, and use the data for the new customer. So in this case, the party ID is going to become now that new ASP. And here’s a handlebar kind of talked about. It’s basically doing conditional. If this value exists, then use this value, else use this instead. And in this case, we’re doing a lookup of the value, and then, of course, the item node here as far as setting that up. And, of course, there’d be a lot of other information you might want on your sales order that you can also add at the header level or be able to do different line level information that you may have associated with setting up a sales order. So the template gives you a sort of a baseline to be able to do the data, but then you can add whatever other fields you might need that might be pertinent to your particular use case or different type of commodities that are being sold. There might be sub-records associated with serial numbers or other things that you might need to be able to add in here, but, again, this kind of gives you sort of a baseline of all the things you may need out of that. Before we create a sales order, we also want to know does that order exist. In this case, we’re doing a logic around ignore existing records. So we’re actually going to do a– there’s different ways you can– there might be a particular field that’s already flagged that your checkboxes say, “Hey, we’ve already sent this item. We don’t need to send it again,” or, “I want to run a dynamic lookup.” In this case, I’m going to look up, see if the order name already exists within SAP ByDesign. And if it does, it will actually skip that record and go on to the next record here. So that allows you some capabilities around how to do the lookups within ByDesign what other parameters you might want to also deal with and then what do you do? You can set default values. You can fill the record, actually show an error, which I’ll show you here in a second, and then be able to say, “Hey, that record already exists,” or, “I don’t want to do it,” or just ignore it and move on. And so that that allows you to be able to have more control over the data itself. Okay. So in our previous example, we were looking at ways to be able to import information SAP Business ByDesign. But now let’s look at the other direction of when we need to get information out. And so normally, we would have a fulfillment. So we want to see the outbound deliveries when those are created that then we can also update, in this case, the Shopify whatever the e-commerce system might be. So let’s take a look at what this looks like. So in SAP ByDesign, what we’re going to do is called next port. This is where we’re exporting data out, and we’re doing this through the Odata layer as far as getting outbound deliveries, collections of the information. Now we do this as a Delta export, so we’re only looking for new outbound deliveries that have been created since the last time the data flow ran. So we just take a sample of what one of those might look like within the preview. We’re actually making a call out to SAP ByDesign. And then you can actually see what the request URL will look like. So we’re getting the information. It’s getting converted to JSON. And so now we have data that we can work with. So that’s how we extract data out doing these different gets, if you will, or lookups of information out of ByDesign. So now that we have these new delivery requests or outbound deliveries, the other thing we need to do is know what the order number was. That information isn’t part of the outbound delivery. So now what we have to do is reference the original sales order that was created in ByDesign that came in from the other data flow. And so we do what’s called a lookup of that sales order to get the information. And there might be other information you’d want to get. But for us, all we’re really doing is just trying to get the external reference number because we need to use that data as part of the reference back to, in this case, Shopify. And so you can see we’re just selecting this external reference and just getting that data back. So we don’t need a large object of all the other information. You can kind of select what data you want the API to return back. And so in this case, we just need the external reference number for that order. And then what we do is we call response mappings that says, “Okay, we will get that external reference, but we’re going to call it order ID which is a heck of a lot easier to work with.” So now you’re able to modify the field names, and so it’s a little more readable. So now when we go into Shopify, we are going to create a fulfillment record. So we have a connector for Shopify. It’s fairly advanced and has a lot of extra bells and whistles. And much like what we saw with the ByDesign connector, we have a large array of different APIs that we can call and different objects. And in this case, we’re just looking up– we’re going to create a new fulfillment using that order number that we had done that look up from from ByDesign. Now the mappings look a little bit different. We have a different mapping tool for Shopify, and this one provides a lot more capabilities. So the way this mapping tool works is on the left you’ll see all the SAP ByDesign fields that we have available for us to do mappings on. As you can see, just sort of our core mappings. Really all we need is a Shopify location tracking number and then what items and the quantities that were shipped with that. But this mapping tool provides a lot more capabilities here. So, for example, you can set a flag for when you want to notify a customer, and they’ll actually get email notification. By default, this occurs. But if you wanted a hard code that value and you can actually just put in a value yes or true or whatever the value that the API requires to be able to do a hard code value, and then that will be set which I won’t say that particular thing. The other things we have available here, too, is say we wanted to– let me get rid of that one. Maybe status, and maybe there’s part of the cancel status code that we get by design. Maybe your order got canceled for whatever reason. So we need to set up some business logic. And there’s different ways we can do that. We could set up a static mapping table. So perhaps it’s one code on one side, another one. So we basically just set up a different lookup table that you can do to convert values that you want that to do from one system to X. So it’s very simple to set something like that up. But we can also set up a business logic utilizing what we call handlebars. So we have a large library of different functions that you can do as far as adding numbers, converting it to Base64 for other things, date formats, if then else type statements, changing the values, doing substring, pretty much anything you need to do to maybe modify, trim, or adjust the data so that the other system can understand it. And it is this case, perhaps we’re going to actually do what we call compare. We’re going to look at one value. And this is sort of how you would do if then else. So we would take that particular field, compare this field. Operator, in this case, would be equals. And then whatever the value that you want, whatever the status code for canceled is, is going to be C. And then because that’s a true statement, it’ll be C. And then if it’s not canceled, it’s probably shipped. And so the value’s going to be S. Som again, then you can also do else statements to be able to come up with the right value based on the business logic. So, again, there’s a lot of capabilities within this, and then maybe there’s a default value, one to use if no value is actually found that you can use to evaluate. So, again, a lot of flexibility as far as the mapping how this would work once it gets sent out and then be able to move this data into Shopify once this is complete. So I’ll get rid of those changes. And so that’s really how we would be able to do this integration from SAP to Shopify in this use case. So once you actually run the data flow, you can see that it’s going to step through each of the steps here, and you can say that I was able to get the record out of Shopify and I set up a error, just made one occur just so we have something to look at here. What happens when an error occurs? We provide information. And in this case, well 404, page not found. I just used a bad URL, so that’s why it got it. But normally, the message here you would see would be exactly what the endpoint is reporting back through the API through the response saying this value doesn’t exist. You need fixes. Unable to find this value. That would actually be recorded here. But the other thing we do is we capture the Json that was actually trying to be processed. So you know exactly which record, which order was being processed in this case and be able to look at the values. And you actually can change the values here. Maybe there’s a status you wanted to add in, or there’s a missing value. Rather than having to go back to the source system, you can just add the value, correct it here, save it, and then retry that data. And then what we’ll do is actually reprocess that particular order for you. And hopefully, it will go in this time based on that update that you made. So that’s allows you to have a very powerful capabilities over the errors that you’re able to manage. We also provide notifications. So let me kind of back out here a level. Each user has the ability to subscribe to data flow events. So in this case, if you want to know whenever there’s an error in particular orders, then you can actually subscribe to that event. And in real-time, once that error occurs, you would get email notification of that particular problem or that error that occurred. And then maybe for the admins, they could also be notified when the connection goes offline. So Shopify is down or Biodesign goes down, you can actually get an email notification. This isn’t so important here, but maybe it’s an FTP site that you’re exchanging with your logistics partner for your 3PL. So you do want to know when that goes down to be able to either file a support ticket or understand why something’s happening. So anyone can subscribe to Integrator.io and get a free account. So if your business users or other people want to be able to have monitor access to these data flows or be able to be notified, it doesn’t always have to be the developers, can actually be the business as owners that can also get notified when there’s an error to be able to fix it too. So again, this is real-time notification to them that they’re able to see and know when things are going right or wrong. And then finally, once your data flow is up and running, you would schedule those flows. We provide a large frequency of how often you want to run these things. You do it every hour, every minute. Or it could be very specific as far as Cron. We can run data flows as often as every five minutes. You have options of maybe particular hours that you want to run it between the hours, every one hour, every three hours, or select the hours during the day that you want to be able to do it. Maybe you want do it at 7 and 18th hour of the day, and that’s the only time you want to do it. So again, we’ll build out the Cron expression for you. For those who actually know what Cron is, you can actually see it being built. But we’ll provide the ability to be able to do it, or maybe you only want to run this flow at the end of the month. So again, the schedule itself is very flexible as far as how often do you want to run this particular flow? Maybe during the holidays, you want to have it running more often than you would say off-peak season. And so again, you have complete control over the frequency of when these things run, and you’re able to do that. One last thing I wanted to also be able to note is anytime you want actually set up one of these flows, you’re able to do a couple of different things. You can clone this flow. So say you’re building this particular flow in your sandbox or tenant in Biodesign., Now you want to migrate this into production. You would actually just clone this, create a new integration tile where these would be housed and then be able– instead of the connection being for sandbox, you want to go to production, and then be able to pick your sandbox or your production accounts, and then be able to migrated into that environment. So it does provide a very simple way to be able to do those migrations. You can name them whatever you want and then be able to clone it. Now, if you are a– let me go back. Should be able to back out of this. Sorry. When you’re actually in the Biodesign environment too, you can also download the different integrations. So this makes a much more portable. So if I was going to move it from one Integrator.io account, you are a system integrator, and you have another account and you want to do this exact same thing, you can do it by flow and actually be able to make it portable. Create your own IO templates. Or you can actually clone the entire integration, all the data flows that are associated with that, and be able to make it very portable. This creates a little zip file that then later you can actually install in another Integrator.io account. So again, we add a lot of portability and allow you to be able to leverage a lot of your hard work and be able to do that. And as partners, we have office hours available to you. Those are published that you can come into a room with an expert and be able to present your problems, show your screen and be able to see exactly what’s going on. We also have our partner success team that is also– you’ll have somebody assigned to you that you can reach out to and also get help when you need to. And then certainly, with our partners, you’re also able to purchase ours. So maybe it’s a large integration that you’re doing for your customer and you want Sligo sort of an advisor on your project or help with solution architecture to be able to review, make sure everything’s looking okay. So that is also services that are available to you as a VAR system integrator.

About The Speaker

Laura Doherty

Head of Strategic Business Development

Laura Doherty, Head of Strategic Business Development at Celigo, works with technology partners to develop integration strategies to expand into new markets, increase sales, and meet customer demand. Laura suspects her time spent in procurement, finance and contracting earlier in her career was the impetus for joining the Celigo team. Integration eliminates painful problems that Laura is passionate about solving with partners to create ideal customer experiences.

Prior to Celigo, Laura worked at Esalen Institute in Big Sur where she collaborated with educators and thought leaders throughout the world to produce hundreds of workshops and events each year.

Chris Bidleman

Director, Integration Solutions

Chris Bidleman is the Director of Solutions Integrations and heads up the Solution Architect team at Celigo. Chris has been with Celigo for over 9 years in a variety of roles including project management and services engineering manager. Prior to Celigo Chris worked with a variety of consulting and software companies focused on solution driven results in healthcare IT and supply chain management with a focus on eProcurement and ecommerce for over 20 years.

Meet Celigo

Celigo automates your quote-to-cash process with an easy & reusable integration platform-as-a-service (iPaaS), trusted by thousands of eCommerce and SaaS companies worldwide.

Use it now and later to expedite integration work without adding more data silos, specialized technical skillsets or one-off projects.