Example: API → Sheets → e-mail
Four built-in steps cover the most common automation of all: take data from one system, keep what matters, write it where people already look, and tell someone. Nothing here is code — and every value moves between steps through bindings.
- Read an API with HTTP Request and filter its answer with Transform
- Write rows to a Google spreadsheet with either way of connecting
- Send an e-mail with the count of what was written
Four steps, no script
The HTTP step’s output is {status, headers, body}; Transform takes output.body.orders and returns the kept list; Google Sheets binds that list to rows, so one step adds every order; the e-mail step binds the Sheets output’s appended count.
Because each step only reads the output of the one before it, you can build and test them one at a time: run the HTTP step alone, look at its answer, then add the next step and bind it to what you saw.
Build it
- Call the API
Under Start add HTTP Request from Apps & data, method GET, and the orders address (or an API (HTTP) connection with a relative address).
- Keep the big orders
Add Transform, bind Input to the HTTP step at
output.body.orders, and filtertotalis at least100. - Add them to the spreadsheet
Add Google Sheets, pick a Google connection, choose the spreadsheet (in Google’s picker, or from the list shared with the service account), its tab, and Add a row. Bind rows to the Transform step’s output.
- Tell the team
Add Send email with a published template that uses
{{count}}, and bindcountto the Sheets step’soutput.appended.
{
"appended": 2,
"range": "Orders!A5:C6"
}Before it runs every day
Publish the flow and add a schedule. A run that adds the same order twice is easy to avoid: switch the Sheets step to Update or add a row and match on id.