FlowRunner
PricingContact
Theme
Start Free

Flickr

Social Media

Search and read Flickr's photo library from your workflows. Agents search photos, fetch photo info and sizes, look up users and their public photos, browse interestingness, and call any other read-level Flickr REST method.

7 actions API key available
Flickr website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A content calendar entry needs imagery for next week's article on a niche topic
Search Photos queries public photos by the topic's tags, with pre-built image URLs in the results
Get Photo Info pulls full metadata for the shortlist, including each photo's license and owner
The agent filters to photos whose license permits the intended use and drops the rest
The surviving candidates post to the content channel with preview URLs, owners, and license names
The editor picks the photo and confirms the license reading before anything is published
Get Photo Sizes resolves the right resolution, and the image and its attribution move into the CMS

What This Integration Enables

Flickr is the deepest public photo archive on the internet for the specific, the local, and the obscure: the 1970s railway station, the regional bird, the industrial process nobody stock-photographs. This connector gives agents read access to all of it. FlowRunner agents search public photos by text, tags, and user, pull full metadata including license, geo, and view counts, enumerate every available size for embedding or archiving, resolve usernames to NSIDs, and browse the daily interestingness ranking. A generic escape hatch calls any other read-level Flickr REST method. Worth stating plainly: this connector is read-only by design. API-key auth covers public read methods, so uploads, edits, and private data are out of scope, which makes it a safe research tool and puts the whole weight of judgment on one question: what are you allowed to do with the photo you found. That question is where the human sits. - Build curated shot lists by tag, topic, or photographer, logged with URLs and metadata - Feed a daily inspiration gallery from Flickr's interestingness ranking - Resolve and follow specific photographers' public streams - Archive originals at full resolution once usage is cleared The metadata itself is quietly valuable beyond sourcing. Geo coordinates, tags, and dates on public photos make Flickr a research corpus: what a location looked like across two decades, how a subject is tagged in the wild, which photographers dominate a niche. Agents can mine that layer through the same read actions without ever touching an image file.

Without FlowRunner

Image sourcing is a browser session Someone searches, opens tabs, squints at license icons, and copies URLs into a doc
License checks happen sometimes Usage rights get verified when someone remembers, which is how takedown emails happen
Community photography goes unused Flickr's decades of niche, geotagged, well-tagged photos are too tedious to mine by hand

With FlowRunner

Shortlists build themselves Agents search by text, tag, and photographer, and deliver candidates with URLs ready to embed
License is a field, not a vibe Every candidate arrives with its license metadata attached, filtered before a human sees it
Niche imagery becomes reachable The long tail of specialist photography is one tag query away from your content pipeline

Use Case Scenarios

The curated shot list with licenses already read

For a campaign on urban cycling, the agent runs Search Photos across the relevant tags, pulls Get Photo Info on the top results, and writes a shot list to [Google Sheets](/integrations/google-sheets): title, owner, license, view count, and the pre-built large-size URL. Photos whose licenses do not fit the use case never make the sheet. The editor opens a list of thirty usable candidates instead of three hundred tabs.

The daily interestingness feed for the design team

Each morning, Get Interesting Photos fetches Flickr's ranking for the previous day and the agent posts the top picks to the design channel in [Slack](/integrations/slack) with title, owner, and image URL. It is a zero-effort inspiration stream with a property stock libraries cannot offer: it is ranked by an algorithm watching what photographers themselves find remarkable, not by what sells.

Following the photographers who cover your niche

The team maintains a list of Flickr photographers who shoot the industry. Find User By Username resolves each to an NSID once, and a weekly flow calls Get User Public Photos for new work, archiving originals via Get Photo Sizes into [Google Drive](/integrations/google-drive) for internal reference, clearly separated from publishable assets. When a shot is worth licensing for real use, the team contacts the photographer, and the workflow has already collected everything needed to ask.

Human-in-Loop Highlight

Get Photo Info returns a license field, and everything irreversible about this connector hangs on how that field gets read. The API will happily hand an agent the original-resolution URL of an all-rights-reserved photograph, and publishing it puts content on your domain that you had no right to use: a write to the public record that a takedown notice, not an API call, eventually reverses. So in FlowRunner workflows the license check is structural, not optional. The agent filters candidates by license before a human ever sees them, but the final publish decision always passes through a person who sees the photo, the owner, and the license name together, because license taxonomies have edge cases and attribution requirements that a filter should narrow, not settle. The archive is enormous and the searching is free. The judgment about what leaves your drafts folder is the part that stays human.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

7 actions

Photos

4
  • Search Photos Searches public photos by free text, tags, or user, with pagination and sorting. Results include owner data and pre-built image URLs, so display needs no follow-up call.
  • Get Photo Info Returns full metadata for one photo: title, description, owner, dates, license, visibility, counts, tags, and geo coordinates when available. The license read every publish decision depends on.
  • Get Photo Sizes Returns every available size for a photo, from thumbnail to original, each with dimensions and a direct source URL. The resolution picker for embedding and archiving.
  • Get Interesting Photos Returns Flickr's most interesting public photos for a given day, ranked by its interestingness algorithm, with the same display-ready extras as search results.

People

2
  • Find User By Username Looks up a user by exact username and returns their NSID, the identifier that user-scoped reads require. An exact match, not a search.
  • Get User Public Photos Returns a user's public photos, newest first, with pagination and display-ready extras. The action behind photographer-following workflows.

Advanced

1
  • Call Flickr Method Escape hatch for any read-level Flickr REST method without a dedicated action, from recent photos to group and gallery lookups. Provide the method name and its parameters; key and format handling are automatic. Methods requiring OAuth-signed user auth are out of scope.

Frequently Asked Questions

What can FlowRunner do with Flickr?

FlowRunner agents can run Search Photos, Get Photo Info, and Get Photo Sizes in Flickr, plus 4 more actions.

Does connecting Flickr to FlowRunner require OAuth?

No. Flickr connects to FlowRunner with an API key, no OAuth flow required.

Can Flickr trigger a FlowRunner workflow automatically?

Flickr doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Flickr

$100 in credits. No card required. Connect in minutes.