Intro to SaaS App Integrations: Build a Flow with Celigo

SaaS companies use many different applications to run their business and being able to connect those apps to automate business processes can accelerate growth. With Celigo you can integrate applications with ease. Our Solutions Consultant will demonstrate how easily by walking through a common use case for companies like yours: building an integration between CRM and Zendesk applications. This session is good for all users (business or technical) whether you are new to Celigo and building your first flow or want a refresher.

Thousands of companies rely on Celigo’s integration platform to enable smoother, more efficient operations with fewer technical resources. With Celigo’s library of pre-built templates and connectors you can get started quickly and expand. 

Topics discussed include:

  • An introduction to the Celigo (new User Interface)
  • Overview of templates, application, and universal connectors
  • Live demo: building an integration flow
  • Overview of Advanced Capabilities
Full Webinar Transcript
Welcome and thank you for joining our session, Intro to SaaS App Integrations: Build a Flow with Celigo My name is Kristie Conner, and I am the Director of Product Marketing for Celigo and I’ll be moderating this session. But the main attraction is Adel Haider, one of our talented solutions consultants. He’s going to be demonstrating how to build a flow from start to finish. We selected a common use case for software companies, connecting Salesforce to Zendesk. This is a great session whether you are new to Celigo or you’ve been using And if you have not already signed up for a free edition account, we’ll highlight how you can sign up during the Q&A at the end of the session. And if you have a free account and have not yet tested the full power of, we’ll tell you how you can activate a 30-day trial. This session is going to be recorded and available On Demand. We look forward to your questions, and so please feel free to start posting them in the panel, and we will get to them during the Q&A at the end of Adel’s presentation. So with that, I would like to turn it over to Adel to do the demonstration. Great stuff. Thank you for that, Kristie. Good morning, good afternoon, good evening, everyone, depending on where you are. So let’s get straight to it. So you’ve seen the agenda there, so we’ll move on to the next step. Before we go on to any demonstrations, let’s do a bit of an intro to Celigo for the case that– if the case or eventuality that you are not familiar with us. So we are a provider of what’s known as an Integration Platform as a Service which allows you to connect a number of different applications in your organization to each other as part of business automation or automating your business processes. Now, we do have deep domain expertise with regards to application integration. We’ve been doing this for a very, very long time. And we have thousands of examples of this which we can leverage in terms of experience as part of that. Now, we are also NetSuite’s largest partner when it comes to these kinds of integrations, and that is relevant for use cases such as these because when connecting to ERPs, for example, that is and can be one of the most challenging types of integrations. Now, we are listed on Gartner’s Magic Quadrant, so we do invite you to have a look there. But more importantly, also, is to have a look at our reviews from some of our customers – quite a few of our customers, I should say – on the G2 website as well. In terms of our platform, it’s actually built for IT but also operations people and lines of business people. So this does not necessarily mean that you have to be very technical in order to understand the platform. That would be good. It’s useful. You can leverage your experience there. But equally, if you are from another department other than IT and operations, you can, in fact, build integrations. So you can leverage your domain expertise in this case as well, and the reason being that this platform is, in fact, best in class for integrations in relation to Software as a Service application. So if you’ve got that domain expertise of how business works, you understand the applications you are using very, very well, then you should be well-equipped to be able to build integrations on Celigo’s platform. And speaking of integrations, there are typically two landscapes when it comes to that, at least, that we’ve seen. Broadly speaking, it’s those in the e-commerce space, the online selling, and also in the software space. And that’s really what we’re going to focus on today, the software. If your business is providing a service of some kind or has a software subscription you are providing to your customers, you will still very likely have a number of applications within your organization that you need to connect. Things like your CRM, your onboarding tool, your subscription management tool and a number of others. Now having said that, even though today we will be focusing on one particular use case, which means two applications in question, and I will talk about those in a moment, we can connect to a number of applications. And what you see there on the screen is just a subset of these. And this is really meant to start to spark in your mind thoughts of what can you do, what applications do you actually use within the business that you might not be aware of the fact that you can and potentially even should be connecting to each other, again, as part of the business automation process. And also, to that event, to that effect, I should say, even though today we will be building a flow from scratch, in practice you do not necessarily have to do that. So we do have what’s known as templates, which are blueprints of integrations, which you can leverage to build integrations as well or to cover any use cases you might have. They are, excuse me, built on best practices as well as from a technical perspective, as well as from a business perspective. And in fact, a lot of customers do use them to leverage their experience, to learn the platform as well, and how to build things on Celigo. And we also have what’s known as integration apps. This is the name we’ve given to what’s known as pre-built integrations. So these are off-the-shelf solutions which live on our platform and they work in a very similar fashion to what you’ll see today. And the idea is if you want to connect to specific systems, such as Salesforce and NetSuite, and you know that you want to do that very quickly and use best practices, again, then you can use an off-the-shelf solution and yet still benefit from using a integration platform, a middle way which allows you to do much more than just connect to systems. It really is about connecting your business at the end of the day. Now, that said, moving on to today’s particular use case, we’ll be focusing on Salesforce and Zendesk. And the particular use case in question or use cases that you might be thinking about for Salesforce, Zendesk are the ones that you see on screen. So things like pushing across accounts from Zendesk as an organization– sorry, accounts from Salesforce, I should say, as an organization in Zendesk cases and tickets, exchanging that information between the two contacts as users as well. Well, in fact, the first three flows, as they’re called on our platform, that you see there, they are actually part of our template. However, today we shall be looking at bringing in orders from Salesforce to Zendesk, which is this flow here that you see at the bottom. And what we’ll do is walk you through how you actually build this from scratch on our platform. Now, with that in mind, I hope everyone is neatly strapped into their seats and their headphones well connected, so they can hear very clearly. We’re going to move on now to the actual platform. Now, when you first log into the platform, what you’ll see is this dashboard. Now, in your case, very likely, it will be an empty dashboard. You won’t have any integrations there unless you subscribe to any pre-built integrations. In my case, these are here just for your benefit for you to see some of the examples that are there. However, we will not be focusing our attention on these today. As I said, we will be building our own integration today from scratch. Before doing that, allow me to provide you some insight into the platform and to what’s there, so you are familiar with what you’re looking at. So here on the left-hand side, you see the home screen, which is essentially what’s here. You also see some tools available to you at your disposal. The flow builder is to build flows, essentially, which is what we will be using. The data loader is for cases where you need to bulk move information for initial loads or initial setup of data into a specific system. Imagine a case where you’re onboarding a completely new application into your business or ultimately replacing, for example, a previous one. You might want to load data into your marketing tool, into your CRM, for example, or even for that matter into your subscription tool as well, and that’s what you would use Data Loader for. For those more adventurous people, you have the dev playground, the developer playground here, which you can experiment with a number of different things, and I do encourage you to do so if you have the inclination. In terms of resources, these are building blocks. These are the actual artifacts that you will be working with and walking through from top to bottom we have connections there. So that’s where you are telling our platform by filling in a form how we should talk to the specific system. So, for example, in this case, we’re connecting to Salesforce. So I will be providing credential information. The same thing for as well. Then we have imports and exports. Now, this is where a lot of the action happens and as the name suggests these are used for importing information into specific systems and exporting information as well and that’s really what you can build in order to do that. They’re part of the flows themselves and I should mention at this point that these are actually reusable artifacts. They are reusable components. So once you’ve built them you can use them in different integrations in different places. Again, for those who are adventurous at heart and perhaps those who like to drink Red Bull and get some wings as it was back in the day, you can of course have and use Javascript scripts within our platform. So, for example, if you want to do some very advanced functionality and have full control of the data that’s flowing through the platform, you can build and write your own scripts and hook them into specific places within the flows themselves. And then, of course, you have some other more advanced functionality there, which we shall leave for another session. Next up as should be expected is the help section. Now, within the help section here you have the help center itself, which is an article, not an article, it’s article housing, it’s a location where you can find a number of different articles written by ourselves, it’s in all of the databases actually, and also by some of our partners as well and inclusive some comments from customers as well, which is always useful. Next up is the What’s New so you can see the release notes and see what new features have been released recently as well as over the last few months and potentially even years as well. It gives you a good view of how our platform has evolved. Last but not least as part of the help section is the submission of tickets. So if you do have any specific issues on the platform at either technical or otherwise and you do require some assistance by all means submit a ticket straight from within the platform. Now, if this is your first time on the platform, then we do advise you to go to the [inaudible] university, and as the name suggests, you do get certified in what you actually do there so there is a learning path, actually, a number of lending paths that you can go on to get more familiar with the platform, better acquainted with the functionality, even though we will cover quite a bit today, but I do encourage you as I said to go through there, to go through the learning path. It is free to go through it and it does give you a good understanding of not only how [inaudible] works but also how integrations work in general, puts you in the right mindset if we can say that way. And last but not least here is a marketplace. Now, here in the marketplace, you will find the pre-built integrations that I shared before. So this is where these are the shelves, which you can browse and see what our company offers, and you can also see templates as well. So, for example, if I go here and I type Salesforce I can see all the pre-built integrations, the integration apps, but also the templates themselves. And you can, in fact, install and use them in your account. Okay. And now I will leave this for another time. In the end here, the aim is to show you how to build an integration from scratch; the beginning. So the first thing you’ll want to do is collapse this here, so we can actually have a full view of things. Step one is creating an integration. Here is, essentially, creating a tile. One of these tiles that we see here. And I’m going to call this build a flow. And I’ll call it software. Hit okay. We’ll save that. And what will happen is this is essentially creating one of these tiles here. And we’ll move straight onto here. Now we can create a flow. Now creation of a flow is where a lot of it actually happens, as I mentioned before. Upon clicking on create flow, what you’ll see is this canvas. Think of it as a painting canvas. An empty canvas where you can start being artistic, let’s say, all right? And the first thing you want to do is actually create an export of information, to extract information out of your source system. Step two will be to actually create an import to push data into your target system. And then, last but not least, you have to create a mapping so that our platform knows how to translate the information between the two systems. And we’re going to go ahead and do that. So in this case I select, there, adding a source. Now you’ll see here at this point you can select any number of 150 plus applications that we already have pre-built connectors for, as well as generic ones. So you can use things like HTTP generic connectors, as well as FTP, for example, for the more legacy systems, and of course databases as well. Now if you go down the list you’ll see quite a few applications that we– systems, SaaS, Software as a Service applications that we have pre-built connectors for and that you can use. Now, of course, if you do not want to browse you can type ahead, which is what I’m doing in this case. Now in this case here, for Salesforce, you have the option of providing an export or a listener. Now this is very important. For those who are familiar with Salesforce will know exactly what this is, for those who are not, this is very, very useful because you then have a real time integration. As soon as something happens in Salesforce then the integration gets triggered. And we’ll show you how you actually configure that today. So we’ll select here the real time option. And then you select your connection. Now, of course, in that case I do already have a connection created, but I will show you what the form looks like in order to create an actual connection to Salesforce, in this case. But nonetheless, for any other ones it’s very similar. In this case you select, for Salesforce, the actual account type, whether was production or sandbox, and then the authentication mechanism which you would like to use. And that’s pretty much it. Once you’ve selected that, you put in the username and then save and authorize the actual account. Now, as I said, I’ve already created that in the interest of time. So I’ll move ahead and use the connection pre-existing. If I continue on now, I will be creating what’s known as a listener. Now even though this has a different name, it is still an export. It’s still extracting information from Salesforce, albeit in a real time fashion. Now for those who are familiar with Salesforce you will see and recognize what this is. Especially if you are familiar with the more admin side of things. If you are not, then fret not, because there’s no problem here. You will be able to easily understand how to use this as Salesforce themselves are very, very good with their documentation. It’s easy to understand what you actually do with a trigger. Now the first step is selecting an actual object type. Now, in this case, I want to extract orders. If you remember from the diagram, it is the orders that I’m interested in. So I type, “Ahead Orders,” and [let’s?] see here we have a number of them to order. Just a plain order is what I’m looking for. Now once I’ve done that, I can then copy this trigger. As you’ll see here, this now says, “Order.” I can copy this and put it into Salesforce. For the purposes of this example, I shall skip that, as the aim is really to focus on our platform, not necessarily on Salesforce. And then there’s some referenced fields. So for example, the order might have associated with it – and will definitely have, in fact – an account and also a contract, for example. Now I might want to get that particular information. So how do I do that? By going into here and selecting, for example, Account I.D., which is the link between an order and an account. It’s typically the account I.D. And then the referenced fields, by clicking this plus sign I actually get a list of all the available fields for the specific connection. So Account Name and Account Numbers are very likely ones which I will be interested in getting, and also, very likely a few others. If we look down the list here, let’s see if we can find a few others which might be of interest to us. Let’s see if we can see anything for now. We might just leave it at that. And I will show you one other thing that you can also do, as well. So apart from actually selecting this, you can also– if we save this. You can also type them into here, as well. So for example, do you know what to reference? You can do this as well, like so. And because I’ve used this quite a number of times already, I already know what to look for. And again, for those who are familiar with the way in which Salesforce works, you can also get related lists. This is very, very useful for those who might have custom objects. So for example, if you’re using a different object other than the opportunities or the items or the opportunity– or the products themselves, if you have a custom one, for whatever reason, then this is where you would access that in relation to the order as long as it’s the child of the order. And of course, you can do the same for opportunities, as well. But now we’re getting very, very technical in terms of Salesforce. So I will kick it back a little bit, let’s say, and show you a bit more about the platform itself. Now one other thing you can do – and again, very useful for scenarios like this in real time – is to be able to define a criteria. Because perhaps not every single order might be of interest. So what I can do here is filter on any of the fields of the order itself, the I.D., any contract I.D., any other information of that nature. If I want to filter on that, I can do it. So for example, I might say that the status of the account might be activated, for example, rather than in draft. So I’ll go ahead and save and close that. Is that actually the case I want to have here? Now if I go ahead and hit Preview, you’ll see that immediately, I actually get some data, straightaway. I can see the information in there, and I can see that there is a number of Celigo, also, fields in there. Because this is a Salesforce account which I have done a few changes on for myself from other scenarios. But nonetheless, you can immediately see their data. And you don’t necessarily have to have that in your case, as well. And that’s it from a listener perspective. Remember, as I said before, for those of you using Salesforce, you will be able to copy this trigger and just paste it into Salesforce. But once that’s done, then you have essentially created a real-time connection. Now if we save and close this, we allow the platform to do what it needs to do in the back end. Oh, I forgot to put a name. This is very, very relevant. So here, let’s call this Listen For Orders. There we go. We’ll save and close that. And there we are. So now we’ve done Step One of the creation of the flow, which is essentially defining the listener. Now we’re going to go over to the other side of things which is the Zendesk sign, so being able to push data into Zendesk. Now, in this particular case, what we’re going to do is actually create two parts to it. We’re going to create an organization as well as a support ticket. Now you might be thinking, “Well, why do we want to do that?” Well, think of it this way. If you’ve placed an order, if you’re a software company, your sales teams have an order, they’ve essentially created a new contract. Things are moving along smoothly. Now you want to move that information across over to your onboarding team to activate the license, for example, or to make any modifications to a license. Then, again, that’s where it’s useful to first verify or create the organization on Zendesk’s side prior to actually creating the ticket, which is what we’re actually going to do. So again, very similar to before, we select Zendesk. And we do have support for both the CRM as well as the support. And that’s what we’re going to look at today. Here, you will also see two options: Import and Look Up. We’re interested in the Import for today. But to give you full visibility, Look Up is for the cases where you need to get data, as well. So imagine here I wanted to get more information from Salesforce before actually pushing to Zendesk. I would be able to do that. As long as I have selected Salesforce there, I’d be able to do that specific operation. Now as I said, I’m interested in Imports, so that’s what we’re going to select. And again, similar to the Salesforce side, I do already have a connection built. But I will show you what the form looks like, just so you have, again, full visibility of how things work. Very similar from the Salesforce perspective, you select the authentication as well as your subdomain. This is specific to Zendesk. the username and password and then you can of course test the connection and save and close. And there you have it. In the interest of time as I said, I will select the pre-existing one and move forward. Now again, here it is now allowing me to create an actual import and you’ll see. Oh, now the specific connection is offline and here is a good opportunity to show you the feedback that you immediately get on the platform. So if for some reason the connection is not as expected the platform will tell you and you have the option to then go and fix it. And the interest of time I will leave it at that but that doesn’t give you the opportunity to show you immediately how interactive the platform actually is. Now in this case here let’s go ahead and create an organization. And what I will do again down here is selecting an API name. Now, in this context, if you are a bit confused, it’s pretty much what Zendesk will offer on their documentation, and even if you’re not technical at all you can still understand what’s happening here. So if we’re trying to create an organization, well, it’s very likely we’ll have an API called organization, and that is in fact the case. Here we go. Organization, itself. That’s the API so that’s the context itself. What operation are we trying to do? Well, we’re trying to create an organization. So very likely be a “create” and there is. So there’s a create and a create an update for the simple– or rather to keep things simple for now, I will simply use create in another instance and/or even if you’d prefer you can in fact use create or update. Now, last but not least all I have to do there is save and close. Now, this import is there but at the moment it wouldn’t do much because there is a missing link which is the mapping. We need to actually map the data between these two systems. So this is where we can actually select here this mapping icon and we can now start mapping fields. But how does it actually work? We’ll, you select here and you see the drop-down, the list– or rather in the dropdown you see the list of all the fields available in this case from Salesforce and these fields are relevant to an audit. In this case, I shall select, for example, an account name to an organization name. Again, you see the drop-down on Zendesk slides are very interactive in that sense. Account number: let’s go with an external ID and you can map any number of other things as well. But for now, again, to keep it simple I’ll leave it at that. And these are simple mappings that we’ve created. You can create more elaborate things which I’ll show in a moment. Now once that is done we still haven’t created the ticket. So the support staff still don’t see anything. Nothing is there. Now what we can do is add another step. And now what we’re doing is creating an orchestrated flow and this means a flow that has multiple steps. So in this case again we’re going to select Zendesk. Yet again it’s going to be inputting data. And again I will use my existing connection even though it is offline for the moment and I will do the same as before giving this a nice name; also create a ticket. And ZD is Zendesk in case you hadn’t guessed from before. It’s just my own naming convention but you can of course choose whichever one most suits you. Same as before we’re going to select tickets in this case and you can type “head”. There we are. We can go to tickets. And then into the operation which is again, you have the create, create or update, delete and update, just singularly. For now, I will select the create but you can, of course, select create or update as well. Saving and closing this will actually add a step here as you can see and if I needed to I would be able to drag this if I needed to drag it to before but I have already placed it in the right place. Now, similar to when I was creating the organization here in this temp, I also have to add a mapping in this as well. And again, just as before, dropdown is available for you so you can, in fact, choose which options you’d like to use. And what I will do– actually, I had forgotten one little step here, but let me continue this and I’ll see if anyone has guessed what it is that might be missing. So in order to create a ticket, I do need a few things here. So I know that I need an organization I.D. I will also need a subject, a description, and an external I.D., very very useful, and when is this ticket due? That’s very useful. Teams tend to really like to have this. Where do I get all this data? Well, let’s go from the bottom up. So here, if I type, for example, start date, well, I’ve got the contract start date. There we go. That will be useful. What about external I.D.? Well, maybe something like the contract number. There we go. So I can use that. Here is something as simple as the description, which is on the order. It can be quite useful for this particular case. But then for the subject, there is a specific naming convention, for example, that you’re using. Well, what about adding a mixture of fields and that is definitely possible. So what you can do, a multi-field option here. Let’s say the naming convention is license provisioning and the specific account number but how– or account name, rather. How do I know what the account name actually is? Well, if I select this field here, I can click here and this will automatically populate the variable or the field which holds the account name, and there you go. Now, we are really creating something with some hard-coded information on the subject of the ticket itself and then as well as some variable information, which is the account name itself. It really is that easy to be able to do this. Now, last but not least is the actual organization I.D. Now, I have not got this information because I didn’t save it from the previous step. So how does it actually work? Well, for now, I shall put here these quotes just for the interest of keeping things as is and I’m going to go back to my previous step and obtain that actual I.D.. Now, if we save and close this, in this particular step after importing the data into Zendesk, in other words after creating the organization, what I can actually do is add a response mapping. So Zendesk will give me the I.D. of the organization, assuming it was successfully created, and I can then take that I.D. and use it in the next step. Now, I will use this naming convention, but again, you can use any which is relevant to your specific organization or whichever one suits you best. Now, if I take this, I save and close that. I can go back into this mapping and, in fact, add in here the missing step. In fact, if I take this away and I start typing ZD, you’ll see that it actually shows up here already. So there I can have a mapping and you’ll notice now how you can daisy-chain, if we can call it that way, the different steps in order to automate how a business process would work if creating an organization or creating a ticket subsequently within Zendesk. Okay. Now, that that is done, the only thing remaining would be to actually start the flow itself or switch it on as it will now. I will give it a more meaningful name, so let’s call this salesforce order to Zendesk ticket and also add only because we have not covered the updates in this particular case. So once we switch this on or enable it, then the flow is actually ready. Now, remember this is a real-time flow. So this would only work if I were to go into Salesforce and make a specific change or create an order. In that case, this would then execute. If it were a non-real-time order, in other words, a scheduled order– a scheduled flow, apologies, then I’d be able to execute the flow as you see here on this little play button. However, in the interest of giving you more information, I will show you later on what that looks like as well. But nonetheless, let me walk you through a few important aspects prior to showing you how that works. So once you’ve built this here, what you also have access to down here is a dashboard. This dashboard shows you every single execution of this flow. So you can see when errors occurred, what is the success of each step, how long it took as well, and how many records were processed as well. You can also see which connections are associated, and you’ll see that if I hover above Salesforce, it is showing me that also here. And if I do the same thing for Zendesk, it also tells me where it’s being used, and it currently is offline. So if I wanted to fix that, I can do that straight from here, edit the connection, and verify whatever issue it’s having or is in place, whatever the error actually is. For those who are more adventurous as I mentioned before, you can execute JavaScript. You can webhook– you can hook, rather, javascript into specific places, and this is how you do that. You essentially select JavaScript here the hook, and you create a script if you haven’t got one already, or you select one which is pre-existing, and you execute the function itself. And there’s a number of different options that you have there at your disposal as well. If we go into it, you will see here that we have specific functions. Some of them are already done for you as what’s known as a stub. It gives you a skeleton function which you can use. Others you can simply create from scratch if you’re adventurous enough and, of course, if you do understand how to use javascript. I cancel out from this, and we take a step back here to show you just a few more aspects of what we see here. You’ll notice here with this schedule, this is actually real-time. As I mentioned before, this is a real-time flow so it requires something happening on Salesforce that’s known as an event B Flow for example. But in this case, if I’ve needed to go to Salesforce to make a change, that’s what would happen for this flow to actually execute. In terms of the entire integration, so suppose I had several flows here, then I could actually see that from the dashboard. And this dashboard will show me every single execution. And in fact, now is a good time to jump over to my sandbox to show you what that actually looks like. So again here, pretty much the same thing. I go into my dashboard, then here is where I can see actual executions. I did this one before in order to give you visibility of what that looks like. As you can see, each step is shown within the actual flow itself. Or each step of the flow I should say is shown within here in the dashboard. You can drill also into the specific step and see what the error was. In this case, of course, reading the description, we can see that there is a missing mapping. And we can, of course, see the retry data as well. Particularly useful in the event of debugging functional errors rather than technical ones. Now if we cancel out from this and close that, we can then go onto a few other very equally important aspects, which are the following. So you can monitor this dashboard if you like, but it’s very likely that you’ve got more important things to do or more valuable things to do. So how do you get notified in the event of an error? Well, this is where the notifications element comes into play. So you can actually select any of the flows that you have or potentially all of them. And what the platform will do is in the event that something does go wrong in any of those flows, the platform sends you an email to say, “There’s been an error. Here is the description of the error. Here’s a link to the actual platform itself.” The same thing would happen offline as well, so in the previous example when I was setting up the system, Zendesk for example was actually offline. So in that particular case then I would get an email to say that Zendesk is actually offline. Now last but not least, if you do have several people having access to your selenium account you can of course then have an audit log to see changes, and it’s very, very useful because in some instances if somebody has made a change to a connection detail, to a certain flow and it no longer works, it is quite useful to have that [inaudible] log here to see that and potentially revert that change as well. And there you have it. That is pretty much how you create a flow from scratch. Now what I will do is move over to here so we can get back into where we were from before, there we are, and bring this into full screen mode. So just as a recap, what we have seen is the building of a flow from an order in Salesforce, pushing that over to a ticket in Zendesk. And as I mentioned before, even though this was the use case for today, there are templates available for you to speed it up as well, the integrations that you might have within your organization. Now from here, where do you actually go? Where do you get started? If this is your first time how do you actually do it? Well, here it is. The first step would be to sign up for a free edition of our Sligo platform. You go straight onto the website you’ll see a very large orange button that you can press and immediately subscribe to and sign up for a free account. You can build your first flow if it is your first time. If it’s not your first time, welcome back. Please go ahead and build some more flows and let us know how that goes. As I mentioned before, I do encourage you to go through the Sligo University and the learning pass available there. It really does help to understand these artifacts and these components in greater detail, to leverage them to the best of their capabilities, and also of your capabilities and your understanding. Now once signed up for a free edition what else can you do? Where would you go from there? Well, what you can do straight from within the platform is sign up for also a 30 day, not three day, it’s 30 day trial. Now the difference between the two, the free edition and the trial, is that with the free edition you can build as many flows as you’d like. However, only one can be active at any given point in time. With a 30 day trial that limitation gets lifted for the 30 days. What this means is you can potentially build automation for your business and experiment and see how that goes for 30 days, having access to things like the templates, and of course connecting several applications as well. And now, let me move over to one final slide here which is the Q and A. So I’d like to open up the panel, Kristie, to see if there are any questions from our audience today. Yes. Thank you, Adel. And I just want to let the audience know we have time for a few more questions so if you want to type some in, we will get to them. So I’m going to kick it off with, can the platform be used to produce files with data from an ERP and upload it to an SFTP? Yes. The answer is yes. That is definitely possible and in fact, that is a very common use case that we see. Okay. Great. And I just want to let everybody know because I’ve gotten this question a couple of times, is that, yes, we are recording the presentation. And we will be sending it out shortly in on-demand form. So you will have access to it. So I have another question. “Can you use to connect multiple systems’ customer data and keep that in sync?” Yes, in fact, you can. And I should say that whoever asked that question, you most certainly can and most certainly should. And that’s why you have that on the screen here, this diagram. And so this is what you would typically see in an organization connecting with Celigo. The idea is to use this as your integration platform, your single platform, your middleware to automate all your different business processes. Ultimately, you will be using several applications throughout the business for different things, and eliminating them blind spots of what is happening is the key to streamlining how business works. And that can really, only be done using a platform designed for the purpose. Great. Thank you, Adel. So we have a question here around GDPR. “Is Celigo and GDPR compliant?” Ah, yes. That is a very interesting question. And the simple answer is yes. And in fact, you can and should. I invite you to go over to this legal website. At the bottom, you will see a security tab. And you’ll have all the details there to see what we are compliant on, how we are compliant on it, and how it actually functions and works. Okay. Great. “Is there a way to build my own connector to a new system?” That’s an interesting one. We get that question a few times, which is a good sign. So the short answer is no. There’s no way for you to be able to build that, simply because that would require us exposing our underlying platform for you to access and make changes too. However, what I will say is, if there is a system that you want us to build a connector for, that you do see that it’s not on the list you can’t find it anywhere in the Celigo website, I strongly encourage you to reach out to us because you never know we might actually already have that on our list, on our roadmap, even for the potential near future. So please do reach out to us in that case. Great. Thank you. Okay. Another question. “Do you have any predefined template which does end to end integration instead of map manually? Yes. That is in fact what I had mentioned before. So these are the prebuilt integration. So cases where you want to connect, for example, Salesforce to NetSuite. This is the most common one that we see. We have a prebuilt integration for this, which means you get it off the shelf. It’s on a subscription basis. You subscribe to the platform as well as the prebuilt integration. It looks and feels very much to what you’ve seen today with the exception that it has a lot of flows already that are prebuilt for you, a lot of fields already mapped for you. It has been built relying on best practice, not only from a technical perspective but also from a business perspective, which is really one of the fundamental– and in fact, one of the biggest unique selling points of Celigo is that we do have these prebuilt integrations in place to speed up and facilitate and really improve integrations as a whole. Right. Thank you, Adel. We have a question around webhooks. “Can we use webhooks on your platform?” Ah, yes. I actually forgot to show that on the platform. Yes, indeed, you can. So long as the source system supports using webhooks, then, yes, you can do it on our platform as well in a very similar fashion to what you’ve seen with Salesforce. Great. We have time for– I think we have time for one more question. Here we go. “Once exported from one end of the flow, does the data live on platform? For example, if the sales order was exported but failed to import the data, is this customer data stored on” Yeah. Okay. Thank you for that. So yes, the answer is, it is stored in the platform for the purposes of retry. So what you saw before where I was actually showing the data for the purposes of modifying it or for retrying, the data is stored on the platform for a maximum of 30 days or until the data has reached its destination, whichever occurs first. At that point, the data is completely eliminated from our servers and which are, of course, running in the cloud securely. And at that point, no longer can data be seen or modified by anyone and for whatever matter. Great. Well, we ended our questions. So with that, I would really like to thank you, Adel and thank the audience for joining us. And if you haven’t signed up for the free edition of Celigo, you can go to, and you can sign up for a free account and get started. So with that, Adel, do you have anything that you would like to add before we close out? Nothing from my end. It was a pleasure to speak to everyone today. And, Kristie, it was a pleasure to speak with you as well. Yes. Thank you so much. And everybody have a great day. Bye-bye. Bye-bye.

About the speakers

Adel Haider

Adel has a software engineering background. He joined Celigo in 2019 having spent the last 10 years within the Enterprise Application Integration space, with a particular focused on Service-Oriented Architectures. Adel began his career as an integration developer in 2009, working at a large IT consulting firm, building integrations using Oracle technologies within several industry verticals. A few years later, he also began working with small businesses developing their online presence by creating web-based applications for various purposes. Today, Adel's primary role is that of Solutions Engineer, supporting organisations in their journey to the cloud, focusing on the use of cloud platforms (PaaS) for their App Integration, App Development and API Management needs.

Kristie Conner