Zapier and Integromat are good solutions for giving your users self-managed, trigger based connections to their apps. On the other hand, hotglue is designed to sit in your product and leads to a simpler connection experience for users – instead of setting up a Zap, users can authorize their 3rd party app and your software takes care of the rest.
Furthermore, with Zapier or Integromat, your users bear the cost of integrating with your platform. On the contrary, an embedded integration moves that cost (if any) to you. This is useful for onboarding purposes, but also to enable more complex integrations. While Zapier and Integromat excel at dealing with a wide range of simple integrations, products that require more data-intensive or complex integrations will find Zapier and Integromat will not meet the need without significant effort.
Paragon Connect is an embeddable, lightweight solution to obtain authorization from users to access their 3rd party apps. It mainly handles authorization, and passes requests through to the 3rd party API. It is not designed to pull and process large amounts of data from systems on its own – Paragon offers a low code workflow builder called Paragon Automate for this purpose.
On the contrary, hotglue is specifically not a low code integration tool – we've found that:
dealing with authorization flows is largely boilerplate, and is not what developers find difficult about creating integrations. Instead, developers want to derive value from their users data. Although hotglue offers similar authorization management and embeddable interface, our focus lies in processing raw data before it reaches your backend.
developers prefer granular control over data, and sacrificing that to a drag and drop editor typically forces developers to write their own preprocessing code on the output data before it's ingestible.
In hotglue, each "type" of data you need your users to import is called a flow.
For example, you may want your users to import Sales and Invoices. When your users first open the hotglue widget they'll see something like the following:
This allows your user to select what they wish to import, and more importantly where they want to import it from. For example, if your user wanted to import Sales data they may be able to import it from any of the following sources:
Flows serve two main purposes:
They let you define what sources of data you want to support for each. For example, for Analytics you may want to support importing data from Google Analytics - but that doesn't make much sense for Accounting
They make it easy for your user to keep track of their data. They know what data your application needs, and how to connect it.
Each flow has a set of supported sources. These are all the sources your users can import data from for that flow.
For instance, my Invoices flow may have the following supported sources:
Files (we want our users to upload their own Invoices as CSV/XLSX)
On the other hand, my Analytics flow may have the following supported sources:
Since hotglue is based on Singer, you can easily create a new Singer tap yourself (for instance, using the Singer SDK) and use it in hotglue.
This way your team is assured you can ship new integrations leveraging the hotglue platform, without waiting on our team. Pretty cool, right?
If you'd like to learn more about this, shoot us an email at [email protected]
Our integration team is available to develop custom taps if needed. Shoot us an email at [email protected] if you'd like to learn more.
Don't see the question you're looking for? Shoot us an email: [email protected]