Integrator Modules
You can find everything that you need to know about Integrator modules and how to use them in this section. Explore how to harness 3rd party services through APIs, staying up-to-date with the latest versions. Dive into five module types: Actions, Searches, Triggers, Aggregators, and Iterators. Actions, the most common type, facilitate data creation, reading, updating, and deletion. Fine-tune module settings, from Dropbox uploads to Email configurations. Maximize control with scenario customization, renaming, scheduling, and more.
To upgrade Gmail or Email apps in Boost.space Integrator, use the DevTool's Swap App function. This involves selecting the old app version, specifying the new version to upgrade to, and executing the swap. This process updates all relevant scenario modules to the latest app version.
Upgrade Google Sheets legacy modules to new ones by cloning your scenario and using Boost.space Integrator DevTool. Replace each legacy module with its new counterpart and transfer configurations manually. Repeat for other apps' legacy modules as necessary.
The lifecycle of Boost.space Integrator apps involves four phases: Beta, Stable, Deprecated, and Shutdown. Apps progress through these phases as they evolve, from initial testing to eventual replacement or discontinuation based on API changes and development updates.
Boost.space Integrator modules are categorized into five types: Actions, Searches, Triggers, Aggregators, and Iterators. Actions process single bundles, Searches handle multiple bundles, Triggers respond to service changes, Aggregators consolidate bundles, and Iterators split arrays into separate bundles.
Module settings enable individual configuration of each module, such as target folders or email addresses, either manually or by mapping items. Connections to user accounts for various services can be established, with mandatory parameters and advanced options available for specific modules.
In Boost.space Integrator, users can specify where to start bundle retrieval in triggers, such as from a specific date or based on bundle IDs, with options displayed in a panel accessible through the trigger icon.
The article explains aggregators, which merge bundles of data into one, with options for grouping and processing. It covers settings like Source Module, Group by, and Stop processing after an empty aggregation.
Iterator modules in Boost.space Integrator convert arrays into separate bundles, enabling individual processing for each array item.
A router in Boost.space Integrator directs scenario flow into different chains based on set conditions, allowing for customized data processing. Routes within the router can be ordered according to specific criteria, with a fallback route handling data that doesn't meet any other conditions.
The Converger concept, not yet available in Boost.space Integrator, aims to streamline scenario routes and reduce duplication. Users can implement alternatives like using a Data store or JSON handling techniques, or creating a separate scenario to consolidate shared sequences.
The article offers guidance on using Text Parser to generate output values using regex expressions and capturing groups. It explains how to extract specific text segments, such as file extensions from filenames, and provides examples of regex patterns and the replace function for achieving this.
The guide outlines the process of replacing legacy modules with new ones to adapt to evolving API versions, ensuring continuous functionality within scenarios even after the deprecation of older APIs.