How Blendr.io connects to your SaaS platform

Saas companies use Blendr.io to scale the creation, deployment and management of native integrations for their customers. For example a CRM company can use Blendr.io to deploy a large number of native integrations between their own CRM platform and other cloud applications such as Sales tools, advertising tools, social media tools etc.

This article describes how the Blendr.io platform interacts with your SaaS platform in order to enable these integrations for your customers.

We make a distinction between two main architectures, depending on the fact if your SaaS platform has an API or not:

  1. Your SaaS platform has an API: Scheduled and Triggered Blends are used
  2. Your SaaS platform does not have an API: your platform will make API calls to Blends

Your SaaS platform has an API

This the classic architecture where Blends (workflows) communicate with your platform using your API, as well as with one or more other platforms using their API as well.

As part of the onboarding process, Blendr.io will add a connector to your platform, based on your existing API. See API requirements to add your Connector on Blendr.io for more information.

The Blends are scheduled or run on a trigger (webhook). In both cases, you could say that the Blend is a middleware that takes care of all the required data synchronization. The Blend will e.g. read data from your platform (for example recently created and updated contacts) and it will send data to another platform. alt text

Your SaaS platform does not have an API

If your SaaS platform does not have an API, you can call Blends using their API endpoint. This architecture means that the execution of Blends is orchestrated from your platform and that you e.g. post data to the Blends and/or get the response from the Blend.

Inside the Blend, API calls are made to other cloud platforms, using their API's. alt text