Tumblr
Social MediaRead public Tumblr blogs from your flows: agents fetch blog metadata, browse published posts, resolve avatars, read publicly shared likes, and discover content by tag across the network.
What This Integration Enables
Tumblr's communities are where certain audiences, fandoms, artists, niche subcultures, actually live, and most brand teams have zero visibility into it. For the brands those communities adopt, the conversation happens with or without them, so the only real choice is whether to hear it. This connector gives FlowRunner agents clean read access to the public network: blog metadata, published posts, avatars, publicly shared likes, and cross-network tag feeds. It is deliberately read-only, public-read API-key auth with no write scope, which makes it a safe, low-friction listening post. - Monitor brand, product, and category tags across the whole network on a schedule - Track specific creator and community blogs for new posts, with type and tag filters - Fetch blog metadata, title, description, post count, last-updated time, for enrichment and reporting - Read a creator's publicly shared likes to understand what they engage with before an outreach - Resolve avatar URLs at exact sizes for dashboards and digest formatting The read-only scope is worth stating plainly: this extension cannot post, reblog, edit, or delete anything, because those operations require OAuth 1.0a signed requests that are deliberately out of its reach. For a monitoring integration, that constraint is a feature. Nothing an agent does through this connector can touch the network it watches. What the agent finds is public; what the brand does about it is not automatic. That response decision is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step lives.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The creator-tracking sheet that stays current
The partnerships team follows 30 creator blogs. Each morning the agent calls Get Blog Posts per blog with a before timestamp of the last run, and appends new posts to [Google Sheets](/integrations/google-sheets) with title, URL, tags, and note count. Get Blog Info refreshes each blog's post count and last-updated time weekly, so dormant creators fall off the active list on evidence, not vibes.
Tag intelligence for the content team
Before planning content for a theme, the team asks what the tag actually looks like. The agent runs Get Posts By Tag for the candidate tags, pulls the recent posts in plain text format, and posts a digest to [Slack](/integrations/slack): top posts by notes, recurring formats, adjacent tags. The content calendar gets built against what the community is actually engaging with this week, and the tag research that used to be an intern's afternoon becomes a standing input to every planning meeting.
Outreach research assembled before the first message
A creator's post about the product takes off. Before anyone reaches out, the agent assembles the profile: Get Blog Info for the blog's description and scale, Get Blog Posts for their recent themes, Get Blog Likes for what they publicly engage with, and Get Blog Avatar for the brief. The partnerships lead reads one summary via [Gmail](/integrations/gmail) and makes the call on outreach with actual context, not a single viral post. Creators can tell the difference between a form letter and a message from someone who did the reading.
Human-in-Loop Highlight
Get Posts By Tag is a read, but what it surfaces demands decisions that are anything but: a fan artist selling merchandise with the brand's characters, a viral post misattributing a quote, a creator whose post deserves official amplification. Every response available, a takedown request, a public reply, a repost, an outreach email, is a public move by the brand in a community with a long memory and a sharp sense for corporate clumsiness. Automating that response is how brands become the cautionary screenshot. So FlowRunner flows on this connector end their autonomous run at classification: the agent sweeps, sorts, and assembles evidence with links and note counts, then hands the flagged items to the community manager. The person chooses the response, or chooses silence, which on Tumblr is often the right answer. The listening is machine work. The speaking never is.
Agent Capabilities
5 actionsBlogs
3- Get Blog Info Retrieves a public blog's title, description, total post count, last-updated timestamp, ask settings, and avatar URLs. Accepts the short name, full host, or a custom domain. The enrichment read behind creator profiles and dormancy checks.
- Get Blog Avatar Returns the direct CDN URL for a blog's avatar at a chosen square size from 16 to 512 pixels. The formatting utility for dashboards and digests.
- Get Blog Likes Retrieves the posts a blog has liked, when the blog shares likes publicly; private-likes blogs return an authorization error. Paginated with limit, offset, and timestamp bounds. The engagement-context read for outreach research.
Posts
2- Get Blog Posts Retrieves a public blog's published posts with post-type and tag filters, pagination by limit and offset, a before timestamp, single-post fetch by ID, and HTML, plain text, or raw output, optionally with reblog and notes metadata. The workhorse behind blog monitoring.
- Get Posts By Tag Retrieves recent public posts across all of Tumblr for a tag, with limit, backward pagination by timestamp, and text-format choice. The network-wide discovery read behind trend and mention sweeps.
Frequently Asked Questions
What can FlowRunner do with Tumblr?
FlowRunner agents can run Get Blog Info, Get Blog Posts, and Get Blog Avatar in Tumblr, plus 2 more actions.
Does connecting Tumblr to FlowRunner require OAuth?
No. Tumblr connects to FlowRunner with an API key, no OAuth flow required.
Can Tumblr trigger a FlowRunner workflow automatically?
Tumblr doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Tumblr
$100 in credits. No card required. Connect in minutes.