Auto-create a Google Photos album from each new Airtable record

Build me an agent workflow that turns every new Airtable record into its own Google Photos album.

Trigger: poll Airtable for a new_record event on a specific base and table I configure. Both the base and table should be configurable inputs. The agent should run once per newly created record.

What the agent should do on each run:

1. Read the Airtable record. If the trigger payload does not already include the full record, fetch it. Also call Get Base Schema for the table so the agent can see the column names and types, and use that schema to decide which field is the title (a single-line text field like Listing Name, Product Name, or Project Name), which fields are the description-ish context fields (things like address, price, owner, specs, SKU, date), which field is the image attachment column (a multipleAttachments field with images), and which URL or text field is the destination column for the Google Photos album link (look for something like Photos album, Gallery, or Album URL). The user will tell me their conventions in the trigger config or in early HITL, but the agent should make a sensible call from the schema if not told.

2. Call Google Photos Create Album with a clean title built from the record's title field. If the title field is empty, fall back to a label like Record {record id}. Hold onto the new album id and productUrl.

3. Iterate every image attachment on the record. For each one, download the attachment bytes from its Airtable-hosted URL, then call Google Photos Upload Bytes to get an upload token. Group the upload tokens and call Google Photos Batch Create Media Items with the new album id so the photos land directly in the album. Stay within the documented batch limits and respect Google's guidance to call batchCreate serially per user.

4. Once the photos are in, call Google Photos Add Enrichment to Album with a short text enrichment built from the record's key context fields (for a listing: address, price, beds and baths, listing agent; for a product: SKU, price, key specs; for a project: client, dates, location). Keep the text tight, a few lines, so the album has the same story as the row. Position it at the start of the album.

5. Call Airtable Update Record to write the album's productUrl back to the destination URL/text column on the same record so anyone clicking through from Airtable lands in the new gallery.

Edge cases to handle: if the record has no image attachments, still create the album and write the link back (so the user can drop photos in later), unless they configure it to skip empty rows. If an attachment fails to upload, keep going with the rest and surface a short summary at the end of what made it in versus what didn't. Don't fail the whole run on one bad image.

Permissions reminder: Google Photos here only sees albums and media this workflow creates, so don't try to read or modify pre-existing user content. The album we just made is fair game because we made it.

Inputs the user should be able to set up front: Airtable base id, Airtable table id, title field name (optional, agent will guess from schema if blank), image attachment field name (optional, agent will guess), context fields to include in the enrichment text (optional list), destination album-link field name (optional, agent will guess), and a skip-empty-records toggle.

Additional information

What does this prompt do?

Watches the Airtable table you pick and fires the moment a new record is created.
Creates a fresh Google Photos album named after the record and pushes every image attachment on the row into it.
Adds a short context note inside the album with the record's key fields so the gallery has the same story as the row.
Writes the album link back to a Photos album URL column on the Airtable record so anyone can jump from the row to the gallery in one click.

What do I need to use this?

An Airtable account with access to the base and table you want to watch.
A Google account where the new photo albums should live.
An Airtable table that has an attachment column for images and a text column ready to hold the album link.
A field on the table the agent can use as the album title (a listing name, product name, project name, or similar).

How can I customize it?

Pick which Airtable table the agent watches, and which column it should use as the album title.
Tell the agent which fields belong in the album's context note (for example address, price, owner for listings, or specs and SKU for products).
Choose where the album link gets written back, or skip the write-back and only build the album.

Frequently asked questions

What kinds of Airtable bases is this useful for?

Anywhere Airtable is the system of record but stakeholders prefer browsing photos in Google Photos. Real estate listings, product catalogs, event recaps, inspection reports, and project trackers all fit the pattern.

Does this work with any Airtable table or only a specific schema?

Any table that has an image attachment column and a field the agent can use as a title. The agent reads the schema and figures out which field is the name, which is the description, and which holds the photos.

Can it see albums I created in Google Photos before connecting this workflow?

No. The Google Photos connection is scoped to albums and photos this workflow creates, so it cannot read or change anything you uploaded yourself or through another app. Each new record gets its own fresh album.

What happens if a record has no image attachments?

The agent will still create the album and write the link back, but the album will be empty until someone adds attachments. You can also have it skip the row entirely. Tell the agent which behavior you want.

Where does the album link end up?

In a column you point to on the same Airtable record. Most teams use a URL or single-line text field called something like Photos album or Gallery.