Functions, standalone module setup, scenario note cloning, and more
6 min
here's a quick look at our most recent product improvements and fixes new functions arraydiff, arrayintersect, set, and escapejson now includes four built in functions, arraydiff, arrayintersect, set, and escapejson , to give you more ways to transform data directly in mapping fields use them to compare arrays, update collections, and prepare raw json with fewer modules key benefits compare arrays use arraydiff(array1; array2) to find new or missing records, and arrayintersect(array1; array2) to find matching records update collections use set(collection or array; key; value) to add or replace fields in a collection without rebuilding the whole structure format json use escapejson(text) to escape quotes, backslashes, and other special characters before sending raw json in webhooks or api calls build scenarios in fewer steps move data by mapping it to a single field instead of using extra iterators, aggregators, filters, or search modules, and reduce overall credit usage availability these functions are available on all plans from the mapping panel or make functions app learn more to learn how to use the new functions, see the documentation array functions https //help make com/array functions ( arraydiff and arrayintersect ) general functions https //help make com/general functions#set ( set ) text and binary functions https //help make com/text and binary functions#escapejson ( escapejson ) configure modules before connecting them you can now configure and run modules before connecting them to the rest of your scenario preview available fields in modules, test sample inputs, and decide next steps based on the actual output key benefits configure first, connect later review available fields in a module and set it up before deciding where it goes in your scenario test with sample inputs run modules with hardcoded values to verify outputs without building the rest of the route check outputs before building see what a module returns before mapping fields, adding filters, or splitting routes, so the scenario is built around actual results build complex scenarios step by step test parts of a scenario separately before connecting them (useful when working with multiple routes and filters) availability this improvement is available on all plans copy notes when cloning a scenario previously, cloning a scenario didn't include its notes now, copies scenario notes too, so your cloned scenario has the same setup tips and handoff details as the original key benefits shared context copy comments and reminders into the cloned scenario, so the next build starts with the same guidance faster reuse naming rules, variable mapping, and other configuration notes stay attached when you clone for a new client, region, or use case learn more to learn how to clone a scenario, see clone a scenario https //help make com/clone a scenario