Use the Blend Editor to build integrations without coding
The Blend Editor is where you build actual integrations.
The Blend Editor is a powerful and flexible visual integration builder. The integration builder comes with pre-built Connector blocks that contain API end-points. Link blocks, map fields, add your business logic by including conditions, variables, and other features to create comprehensive integrations for your customers.
Blendr.io supports big data as well as hyper-scalable and distributed execution to manage billions of data records.
Schedule integrations to run during a certain time frame, at a certain time or with a fixed frequency.
Blendr.io empowers SaaS companies to build integrations in a scalable and secure manner, up to 10 times faster than “classic” development.
In this webinar we will cover how you can build and embed multiple integrations to your SaaS platform.
The integration builder offers a set of powerful features to answer all your integration requirements
You can call a Blend from within another Blend. Use the “Call” block to call a webhook URL from another system inside a Blend.
Each Blend is automatically exposed as a REST API endpoint, so it can be called as a webhook URL to execute the Blend.
Temporarily or permanently store any type of items, e.g. Contacts, Products, Orders, etc. to keep track of the status for each item.
Stop or pause the execution of the Blend. The Sleep block causes the Blend to wait and is handy if you want to pace the execution.
Choose when and how often your integration is executed – only once or select a frequency, the start and the end dates.
The large amounts of incoming webhooks can be processed efficiently within one run (job) of the triggered Blend.
Use and combine formulas inside placeholders, to manipulate data. The formula will be applied to the result of the placeholder.
Find common or unique items between 2 given lists (arrays). Objects are compared based on the values from the keys you entered.
Iterate over items in a list to process items one by one. You can use the block “Exit loop” to stop processing the items in the loop.
A variable has a name and type and can store data while the Blend is running. Use variables to temporarily store and transform data.
Use the Data Store as a permanent data storage or as a temporary data cache. Configure caching on individual Blend blocks.
Make your flow conditional, for example, do this when X is true, and do something else otherwise.
Limit the number of items in a list, e.g. the amount of data when you are testing the Blend.
Execute blocks in different parts of your Blend. Add the blocks below a “Label” block, and use “Go To Label” blocks to jump to the Label block, from elsewhere in your Blend.
Remove duplicates from a list. Objects will be compared based on one given key. If the values of the key are the same, all but one object will be removed from the output.
Merge two given lists (arrays) into one new list. The items of both input lists will be added to the new output list and matched based on a given key.
Replace keys with new keys, for objects in a list (array).
Find an object in a list (array) of objects.
Filter a list (array) of objects based on one or more conditions.
Redirect a user to a specific URL (e.g. a detail page of a contact in a CRM) after running a Blend.
Add a case statement with a condition and multiple cases based on the result of the condition.
Compare the keys of two objects and get the keys that are different or the same between both objects.
Build transactional Blends that retry a transaction when it fails. The number of retries and time between retries can be configured. Failed transactions (runs of triggered Blends) will be retried by putting them on the queue again (DLQ concept).