Below you can find our growing library of tutorial videos that gives you good input of how to use Corbit.
Define your source, the input for your workflow. This can be a folder, an email account, FTP server, or even just a date/time.
What should your workflow look for in the defined source? This is what you use a filter for, create your own filters or use any of the pre-defined filters.
This is where the exciting part happens. What is the action you want to perform. Maybe it's just a simple copy of a file, or a more complex REST API call to a 3rd party system.
In this video you will learn the basics and get ready to move files around.
In this video you will learn how you setup multiple filters and mulitple actions
In this video you will learn the basics regarding macros
in Corbit
In this video you will learn how to add specific parameters to a macro.
In this video you will learn the basics of the CASE macro in the most simplest form.
Variable data is used in many workflows, in Corbit we call this BUCKETs. Essentially it's a holder for data that is picked up and can be used in other parts of your workflow.
This video will show you how to read an XML file, save data as BUCKET values and reuse those values when updating a database
A Corbit workflow always start with a Source. All sources can be configured to run every so often, every 15 seconds or maybe only once a day Mon-Fri at 23:00, endless possibilities.
A source can be any of the following:
Once a source has been triggered by a file or a specifc time of a day, there has to be a filter. This means that Corbit needs to know what to look for in the specifc source. For example if you want to read JPEG from an FTP server, then you have the FTP Source and use a JPEG Filter.
A Filter can be setup with the following:
Note
All filters can be configured with more than one condition. If you for example use File filter, you can setup several conditions, i.e. file extension should be *.jpg and file size should be more than 5 Mb.
A Corbit workflow consists of three components, Source, Filter and Action. Your workflow can have more than one of each, for example one action to copy a flie and then move.
An action can be any of the following:
Corbit can do a lot of different tasks. For those tasks that are not built-in there is most likely a Command Line application that can be used, and THAT can be automated by Corbit. It can for example be that you have bat file or shell script that you want to execute, and of course also an actual application.
Nobody likes to wait, but sometimes a workflow has to wait for a confirmation that it can continue. I.e. if value X is not set to GO, don´t do anything. Then it should wait until value X is GO. It can also be a date/time that has to pass before the workflow continues.
Corbit can sometimes be very complex and sometimes you just need a helping hand to get started. Please don't hesitate to contact us if you have any issues at all.
If you rather talk to someone, please call us at +46 11 12 75 80.