Understanding Operations in Integration Scenarios: Maximizing Efficiency with Boost.space

OperationsAn operation is a task performed by module. are related to our integration scenariosA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive.. Whenever any task is performed by your integration, it counts as an operationAn operation is a task performed by module.. It is very similar to Zaps in Zapier or Operations in Make. If you run out of your operations, your data synchronization scenarios will stop. Operations are refreshed each month or you can also upgrade your Tier. Typically it takes between 2-4 operations to sync one record to or out of Boost.space (this depends on the third-party tool and the complexity of your integration scenarios). During the first sync, usually, all records are synchronized, and then only changes get updated across your tools, optimizing the number of operations consumed. Please keep in mind that this depends/varies on the possibilities of your source or destination third-party tools.

For example, when your scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. reads a record from Pipedrive, or writes a row into a Google sheet each counts as one operation.

More examples that count as operations

• read data from an app or webhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers.
• search for data in an app
• create data in an app
• update data in an app
• delete data from an app
• transform data using the built-in tools
• aggregate a row of data into an arrayWithin a bundle, data items of the same type are sometimes in an array. You can find an array by looking at the details of a bundle. Depending on the details of your scenario, you can map other modules to a specific item in an array or use iterators and aggregators to manipulate your data into other formats. When mapping,... or text
• iterate a row of data

Depending on the complexity of the process you’re automating, your scenario can perform anywhere from two operations to thousands of operations in a single run.

Don’t worry about using up all your operations before the end of the month or year. You can always buy extra operations or upgrade to a higher tier plan.

• Error handler modules (Rollback, Break, Resume, Commit, Ignore) – no operations counted
• RouterA router allows you to add new routes to a scenario so you can branch your flow into several routes and process the data within each route differently. module – no operations counted
• Sleep module – consumes operations, but doesn’t consume data

If you have any additional questions, please do not hesitate to reach out to us at [email protected].