Fixes from playing every Showcase

• An AI agent after a WhatsApp message event now reads the message even when its Message setting names a field the event does not have.
• Nearby places leaves a city, street or phone empty where the database only says Unknown.
• Ask xMap builds the flow with a My data block for your own stores, sites or customers instead of asking which table to use: you pick the table in the block.
• A Nearby places search that the database fails once is tried again, and a search that still fails says which one and why.
• Travel area on Automatic after an Area of interest draws its area around that place (for example 15 minutes by bike from a workshop), instead of asking for places.
• A data block that searches an area after another block now says that the items coming into it were not passed on, and how to keep both.
• Regional data records whose district or name the source left as "-" are named by their kind and city (Apartment in Jeddah), and leftover shape fields are dropped.
• A test run of a flow that starts on an app event (Excel, WhatsApp...) runs on the app’s example even before its own settings are filled in.
• Sort and limit keeps the order and says why when its field is there but empty (a calculated field that divided by 0), instead of stopping the run; Calculated field says when a division by 0 left a value empty.
• Nearby places understands more everyday words: metro station, train station, noodle bar, training school, childcare centre, coworking, tutoring centre, physiotherapist, vet; and a word such as clinic alone no longer picks an unrelated kind of place (physio clinic was read as a TB clinic).
• A flow that starts on an app event whose own example is empty (one of Google Calendar’s) test-runs on another example of the same app.
• AI assistants and the API can delete a table from My data: the MCP tool delete_table and DELETE /v1/tables/{id} (see the API reference).
• A test run of a Chat flow sends a plain hello, which any assistant can answer, instead of a question about cafes.
• A Filter on a field that every item left empty (ships that sent no destination) keeps none and says so, instead of stopping the run.
• xMap LLM set to Classify takes labels one per line as well as separated by commas.
• Ask xMap puts a search that brings its own items (News, Web page watch) beside the block before it, so neither one’s results are lost, and keeps searches around each place found small enough for a test run.
• Job postings within a distance keeps a posting that only names a big city (London) when the place searched is in or near it.
• Property changes on its first look reads the county’s latest update when there was none in the last 7 days but one in the last month.
• A Nearby places search that the database briefly says it has no data for is tried again, and a very big search that keeps timing out asks for fewer places.
• A test run of a block that searches around each incoming item (a table of 100 stores, say) checks the first 20 and says so, so the test ends in minutes; Run once does them all.
• Items that have an address but no position (entries read from a web page, rows of a sheet) are placed from their address before a block searches around them.
• Match with my table gives an item with no position of its own the position of the row it matched (a member’s home), so the blocks after it can work around it.
• A Filter or Branch on a number such as Jam factor that came back empty for every item keeps none this time and says so.
• Ask xMap places areas it is given by a long name, uses the Area of interest for blocks that have nothing coming in, and never writes a name where an email address goes.
• xMap LLM set to Classify keeps its labels whatever the field is called: a field named like building_fit was read as a score and every label was lost.
• Weather forecast asks for fewer places at a time and splits a call that takes too long, so forecasts for a long list of places come back.
• Calculated field reads || and && as or and and, as written in spreadsheets.
• Property changes on its first look also reads the county’s latest update when every update in the last 7 days was a full reload.
• A test run of a new Web page watch passes on what is on the page now, marked as examples, so you can check the rest of the flow; real runs still send only what is new or changed.
• A Filter on Rating or Reviews after Apollo reads each contact’s company rating, and a Filter on wind_max_kmh, temp_max or rain_total_mm also reads hour-by-hour forecasts.
• A flow that starts on an app event can be checked and deployed when blocks after it work around a place: the event’s example gets a sample position for the check.
• Sort and limit on a field no item has (it comes from a search that found nothing) keeps the order and says so, instead of stopping the run.
• Items with latitude and longitude columns under those names (a city’s open data) are placed by them, also entries read by Web page watch, and an address is looked up with its borough or district.
• Web page watch reads long lists of many fields, asking again for the first 20 when a page is too long to read at once.
• Map business scan around each incoming place with nothing coming in says so and goes on, instead of stopping the run.

Every update · Help center