Save Typeform photo submissions to a Google Photos album and ping Slack

Build an agent workflow that catches every new Typeform submission with photo or video uploads, files the media into a dedicated Google Photos album, then announces the entry in Slack.

Trigger: a Typeform outgoing webhook on the form_response event for a specific form. When a submission arrives, the agent should:

1. Read the response. Use Typeform Retrieve Responses to load the full response (or work from the webhook payload), and identify which answers are file uploads. For each file URL, call Typeform Get Response File to pull the bytes.

2. Find or create the destination album in Google Photos. The album title pattern is the form name plus the current month and year, for example "Customer Testimonials – June 2026". Search existing app-created albums first; if none matches, call Google Photos Create Album. Cache the album id for the rest of the run.

3. Upload each photo or video with Google Photos Upload Bytes to get an upload token, then call Batch Create Media Items with the upload token and the album id so each item lands directly in the album. If an item already exists, use Add Media Items to Album instead.

4. Add a short text enrichment to the album with Add Enrichment to Album. The text should include the submitter's name, the submission date, and any caption answer the form collected, so the album reads like a curated feed and not a dump.

5. Post a Slack notification with Slack Bot Send a Message to a configured channel. The message should include the submitter, form title, how many files were filed, and the album link (the productUrl returned by Google Photos).

Owner-configurable inputs: the Typeform form id, the Slack channel id, the album naming pattern (default "{form name} – {month YYYY}"), and a field mapping that tells the agent which Typeform answer to treat as the submitter name and which to treat as the caption.

Edge cases: if a submission has no file uploads, skip the Google Photos work and either skip Slack or post a lighter "new response, no files" note depending on the owner's preference. Keep in mind the Google Photos app-created data constraint: the album and items live under the connected Google Photos credential and are separate from the user's personal albums, which is exactly what you want for a curated submissions archive. Prefer Slack Bot over the user Slack integration so the announcement reads as a workflow notification, not as a specific person.

Typical use cases this seeds: photo contests, customer testimonials, employee headshot collection, real estate listing submissions, and field service before-and-after photo capture.