API research to Google Sheets
Fetch a public sample record, check its fields, prepare a research row, and verify the live write to Google Sheets.
Live exampleBefore you run it
Recorded live with fictional JSONPlaceholder data. The matching branch was tested; test missing-email and missing-website cases before adapting this example. Repeating Append creates another row.
Read the related guide Open your canvas Download example workflow Download sample workbookImport the workbook into Google Sheets. Import the workflow JSON, then choose your own connections and spreadsheet. Review every action before a live test.
Includes a recorded live example using demo data. Configuration close-ups and callouts explain the steps.English narration generated with Kokoro Heart.
Try it step by step
1. From an API to a useful research row
Research workflows are useful when data arrives in a consistent format. This example fetches one fictional company, checks its contact fields, and saves a useful research row in Google Sheets.
THE USE CASEFetch → Check → Prepare → Save2. Fetch a company record
Set the HTTP request to GET and choose the public JSONPlaceholder users endpoint. This returns sample data for tutorials. Expression then passes the response body to the following checks.
01 / HTTP REQUESTGET · /users/13. Let useful records continue
The Filter requires an email. Condition checks whether a website is present, then selects the Ready route. Match the outgoing edge label to that branch. A missing email stops this branch.
02 / FILTER + CONDITION{{steps.select.result.email}}4. Prepare the destination columns
Transform prepares the company title, website URL, and source label. A one-second Delay follows. Google Sheets maps those three fields into the Research tab, using Append mode.
03 / TRANSFORM + DELAYtitle · url · source5. Watch the actual workflow run
This is the actual screen recording of the live test. The request succeeded, the rules matched, the delay completed, and Google Sheets confirmed the append. The execution log reports eight successful steps.
04 / LIVE EXECUTIONHTTP 200 → rules matched → row written6. Verify the destination, not just the log
The Research tab contains the new row. This pattern is useful for internal research lists, enrichment pipelines, and lightweight reporting. Replace the sample API with your authorized source, and test rejected inputs before expanding it.
THE RESULTRomaguera-Crona · Public demo API
Read the English transcript
Research workflows are useful when data arrives in a consistent format. This example fetches one fictional company, checks its contact fields, and saves a useful research row in Google Sheets.
Set the HTTP request to GET and choose the public JSONPlaceholder users endpoint. This returns sample data for tutorials. Expression then passes the response body to the following checks.
The Filter requires an email. Condition checks whether a website is present, then selects the Ready route. Match the outgoing edge label to that branch. A missing email stops this branch.
Transform prepares the company title, website URL, and source label. A one-second Delay follows. Google Sheets maps those three fields into the Research tab, using Append mode.
This is the actual screen recording of the live test. The request succeeded, the rules matched, the delay completed, and Google Sheets confirmed the append. The execution log reports eight successful steps.
The Research tab contains the new row. This pattern is useful for internal research lists, enrichment pipelines, and lightweight reporting. Replace the sample API with your authorized source, and test rejected inputs before expanding it.