Yes, hotglue does support bidirectional syncing! When creating a flow, you choose what source 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 integrations, the source would be the third party data source and the target would be your product (such as your API, database, etc.).
For a flow where you want to push data from your app to your customers third party integrations, the source would be your product (or our API source) and the target would be the third party integration.
hotglue supports real-time triggers for many of our integrations. For example, hotglue can automatically trigger a sync job when a new contact is created in Salesforce, or when a new order is placed in Shopify.
However, hotglue is primarily designed for bulk use cases where you need to clone historical data from an integration and incrementally sync new data and updates to your product (and back to the 3rd party integration).
To learn more, book a demo with our team.
hotglue is designed to sync data incrementally, meaning the first sync job pulls all historical data (from a specific start date), and subsequent sync jobs only pull the delta data (new or updated records).
hotglue has no specific limitations on the data size per sync, and can adjust these based on your subscription plan. To learn more, shoot us an email at [email protected].
Many iPaaS solutions only handle authorization and pass requests through to the 3rd party API. They are not designed to pull/push and process large amounts of data from systems on their own – additionally, many are low code tools with very narrow possible use cases.
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 an 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 is ingestible.
hotglue has over 100 connectors in closed beta – if you'd like an integration that is not listed on our connectors page, 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 maintains flexibility over shipping new integrations even while leveraging the hotglue platform.
If you'd like to learn more about this, shoot us an email at [email protected]
Yes! Our integrations team is available to develop new connectors if needed. In fact, all of our paid plans come with service hours that can be used towards building new connectors.
Shoot us an email at [email protected] if you'd like to learn more.
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.
Don't see the question you're looking for? Shoot us an email: [email protected]
Updated 2 months ago