How does hotglue compare to Zapier or Integromat?

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.


How does hotglue compare to Paragon Connect?

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:

  1. 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.
  2. 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 is ingestible.
hotglue field selector + Python preprocessing layerhotglue field selector + Python preprocessing layer

hotglue field selector + Python preprocessing layer


Does hotglue support bidirectional syncing?

Yes, hotglue does support bidirectional syncing! When creating a flow, you choose what tap you want to pull data out of and what target you want to send data to.

For a flow where you want to pull data to your software from your customers third party data sources, the tap would be the third party data source and the target would be your product.

For a flow where you want to push data from your app to third party data sources, the tap will be your product and the target would be the third party data source.


What if I want a source that isn't currently available?

📘

hotglue has over 100 connectors in closed beta – if you'd like to use a source that is not listed, contact us and we can enable the beta connectors for your account.

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]


What if I don't want to develop it myself?

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.


Something else

Don't see the question you're looking for? Shoot us an email: [email protected]


Did this page help you?