We use itDuzzit to build most of our integration projects. Why use a third party tool instead of an application programming language like Java, C# or Ruby to do integrations? Here are a few reasons!
There are already tons of applications available in the itDuzzit Connector Library. In other words, if the app you need to use is in the library, there's a good chance you can just focus on things like mapping fields between the apps, not writing brand new API calls. This library is composed of connectors, and these connectors are the building blocks you can use to build integrations. Once you know how to chain together different connectors you can build sophisticated integrations very, very quickly.
Build in Parsing Features
If you've ever had to parse XML or JSON and spent hours agonizing over which parser libraries are best to use, then you know how much of a time-drag just doing basic data manipulation can be. itDuzzit has a lot of nice feature for parsing XML and JSON (I'll cover this in a separate blog entry). There are also some nice "easter egg" features you can use for parsing comma separated lists, and iterating through lines of files. Once you know the tricks of these parsing features, you can save a lot of time processing data.
Great Triggering Options
One tricky aspect of deploying integrations like this is knowing "when" to kick off the exchange of data. Yes, many apps today offer webhooks, that provide a convenient external configuration method invoking an integration, but many more apps do not include webhooks as an option. Luckily, using a platform like itDuzzit gives you a lot of options. For one, you can easily schedule just about any duzzit you build and have it execute on a scheduled basis. You can also build your own "polling-style" integrations: these are jobs that run on a near real time basis (say every 15 minutes) that "wake up" and check for new data to be sent to another itDuzzit endpoint. What's particularly nice about polling style duzzits is that they look and feel just like a lot of webhook-style connectors, which means you don't have to care about these implementation details very much.
Built-in Logging and Notifications
Bad stuff happens - in any integration. Wouldn't you rather know when bad stuff happens? I would! The nice thing about itDuzzit is that you have access to how your integrations are doing via the Logs page. The itDuzzit platform is smart enough to notify you by email if something goes wrong with any of your integrations. If you've written a custom integration, you don't need to add any specific logging code to your duzzit, just make sure that you have a boolean output variable called success and a text output variable called error (which is where you dump any error messages you like), and the platform will do the rest.
I'll go into more detail on how to use all these features in more detail in successive posts.