Menu

Mattering Automations Tumblr integration

Connect Tumblr to Mattering Automations: public blog reads and the network-wide tag feed, your dashboard, drafts, queue, submissions, notifications and blocks, and publishing, reblogging, liking, following and queue management, from one credential whose OAuth tokens never expire.

The Mattering Automations Tumblr integration puts Tumblr API v2 on your automation canvas: read any public blog's posts, notes, likes, pages and avatar and the network-wide tag feed, read your own dashboard, drafts, queue, submissions, notifications, followers and blocks, and publish, edit, reblog, delete, like, follow, block, mute, filter tags and manage the queue. 37 nodes in total, 22 reads and 15 actions.

The credential is a single Tumblr application credential with up to four values, and it is unusual in one useful way: it degrades rather than failing. The OAuth Consumer Key on its own is a valid saved credential that runs the seven public read nodes, and Test Connection reports a read-only connection and names what is missing. Add the consumer secret and an OAuth token and token secret and the same credential unlocks the other thirty. Tumblr's OAuth 1.0a tokens never expire, so setup is a one-time step with nothing to refresh later.

One thing to settle before you build anything that writes. Tumblr is a public, federated network, and this integration does not soften that. A published post reaches every follower's dashboard immediately and can be reblogged within seconds, and a reblog is an independent post on somebody else's blog carrying its own copy of your content. Nine nodes are flagged destructive for that reason, and the recommended pattern throughout this guide is to write with the post state set to draft or queue so a person approves in the Tumblr app before anything is published.

Before you start

  • A Tumblr account, and a Tumblr application registered at tumblr.com/oauth/apps. Registration is free and immediate, with no review and no paid API tier.
  • A decision about which half of the API you need. The OAuth Consumer Key alone runs Tumblr: Get Blog Info, Tumblr: Get Blog Posts, Tumblr: Get Tagged Posts, Tumblr: Get Post Notes, Tumblr: Get Blog Likes, Tumblr: Get Blog Avatar and Tumblr: List Blog Pages. Everything else, including every write, needs the full four-value credential.
  • For the user-scoped half, a one-time authorization of your own account through Tumblr's developer API console at api.tumblr.com/console, which runs the three-legged OAuth 1.0a flow for you and shows the resulting token and token secret. Because Tumblr's tokens do not expire, this is never repeated.
  • A blog you are willing to write to, if you intend to use the action nodes. Tumblr has no sandbox: a test post is a real post on a real blog, visible to real people. A throwaway blog on the same account is the usual answer, and the blog picker on the write nodes lists every blog the credential can act as.
  • An awareness of Tumblr's published ceilings before you design a loop. Per registered application, 1,000 requests an hour and 5,000 a day. Per account per day, 250 published posts, 250 image uploads, 200 follows and 1,000 likes. The blocks endpoints carry their own ceiling of 60 requests a minute. Tumblr: Get Account Limits reads what is left of the write budget.
  • A Mattering workspace with access to the Automations app.

Register a Tumblr application and get your OAuth values

Tumblr splits its API into a public half authenticated by a consumer key sent as a query parameter, and a user-scoped half authenticated by signed OAuth 1.0a requests. One credential in Mattering covers both. Only the consumer key is mandatory, so you can connect a read-only credential first and complete it later without rebuilding anything.

Sign in to Tumblr and open tumblr.com/oauth/apps, then register an application. The form asks for a name, a description and a callback URL; any URL you control is fine, because you will not be running a hosted consent flow.
Copy the OAuth Consumer Key and the OAuth Consumer Secret shown on that application. If you only need public reads, the consumer key is all you need.
The consumer key is not treated as a secret by Tumblr: it doubles as the api_key query parameter on public reads, so it travels in request URLs by design. The consumer secret, the OAuth token and the token secret are secrets and are stored encrypted.
For the user-scoped half, open Tumblr's developer API console at api.tumblr.com/console and authorize your own account against this application. The console performs the three-legged flow and shows the resulting OAuth Token and OAuth Token Secret. Copy both.
Tumblr's OAuth 1.0a tokens never expire and never rotate, so this is genuinely a one-time step. There is nothing to refresh, no consent to renew, and no expiry date to diary.
The token identifies the Tumblr ACCOUNT this connection acts as, and everything it publishes, likes, follows or blocks is attributed to that account in public. Authorize the account you actually want automations to speak as, not whichever one happened to be signed in.

Connect Tumblr to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Tumblr from the list.
Click Create new credential. Paste the OAuth Consumer Key, and then the OAuth Consumer Secret, OAuth Token and OAuth Token Secret if you have them. Save.
Leaving the last three fields empty is a supported choice, not an incomplete form. The credential saves, the seven public read nodes work, and the user-scoped nodes refuse locally with a message naming exactly which values are missing rather than sending a request that would fail as an unexplained 401.
Click Test Connection. With all four values, Mattering signs a request to Tumblr's account endpoint and reports the account name and every blog it can act as, so a credential pointed at the wrong Tumblr account fails loudly instead of quietly returning somebody else's perfectly good data. With the consumer key alone, it reads the public tag feed instead and reports a read-only connection along with the values that are missing.
Click Connect. All 37 Tumblr nodes appear in your canvas palette.

Verify it works

Start on the public half, because it works whichever credential you saved. Drop Tumblr: Get Blog Info onto a canvas, put a well-known public blog such as staff.tumblr.com in Blog Identifier, and run a test step. You should get the blog's title, description, post and like counts and its UUID under data.response.blog. Note the shape while you are here: Tumblr wraps every response, success and failure alike, so every path on every node in this integration begins at data.response and never at data directly.

If you saved the full credential, verify the signed half too, because a public read proves nothing about it. Drop Tumblr: Get Account Info onto the canvas and run it with no configuration at all. It reports the account this connection is authenticated as and lists every blog it can act as at data.response.user.blogs[], with each blog's name, title, URL, follower count, queue depth and draft count. This is also the node that fills the blog picker on every write node, so a successful run here means those pickers will populate.

Finally, confirm the picker itself. Drop Tumblr: Get Draft Posts onto the canvas and open its Blog Identifier field: it should list your own blogs by title with their URLs underneath, rather than being a free-text box. Choose one and run the step. Everything in this verify path is read-only, so none of it can reach the nine destructive nodes, and it is safe to re-run at any time.

Node reference

37 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 22

Tumblr: Check Followed By

tumblr_check_followed_by

Ask whether one specific blog follows one of yours, answered as a single boolean at data.response.followed_by. Much cheaper than paging a large follower list to find out, which is what makes it the right node inside a loop over a list of prospects. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Account Following

tumblr_get_user_following

List the blogs the connected account follows, at data.response.blogs[], with a total at data.response.total_blogs. Each row carries the blog's name, URL, description and last-updated timestamp, so this doubles as a way to spot followed blogs that have gone quiet. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Account Info

tumblr_get_user_info

Report the account this connection is authenticated as, and list every blog it can act as at data.response.user.blogs[] with each blog's name, title, URL, follower count, queue depth and draft count. This is the node that powers the blog picker on every write node in this connector, and the one to run first when another node returns an unexpected 401. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Account Likes

tumblr_get_user_likes

Read the posts the connected account has liked, whether or not the account shares its likes publicly - which is what makes this different from Tumblr: Get Blog Likes. Use it to turn a reading habit into a curated digest, or to sync liked posts into a datatable. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Account Limits

tumblr_get_user_limits

Read how much of the account's daily write budget is left: posts, photos, follows, likes, new blogs and video minutes, each with its ceiling, its remaining count and when it resets. Run this BEFORE a loop that posts or follows, because Tumblr rejects the request that crosses the line rather than slowing down, and the workflow has no other way to see it coming. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Blog Avatar

tumblr_get_blog_avatar

Get the URL of a blog's avatar at a chosen size. Useful for enriching a contact record or building a digest with pictures. Tumblr answers this one two different ways - a redirect to the image for an unsigned request, JSON for a signed one - so this node normalizes both into data.response.avatar_url and never downloads the image itself.

Tumblr: Get Blog Followers

tumblr_get_blog_followers

List the blogs following one of YOUR blogs, at data.response.users[], with a total at data.response.total_users. Each row says whether you follow them back. Only works on a blog the credential owns - a blog's follower list is private to its owner. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Blog Following

tumblr_get_blog_following

List the blogs one of YOUR blogs follows, at data.response.blogs[]. This is the per-blog view; Tumblr: Get Account Following is the account-wide one and returns the same shape for the primary blog. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Blog Info

tumblr_get_blog_info

Read any public blog's profile: title, description, post and like counts, avatar, ask settings, its UUID, and whether the connected account already follows it. Works on a consumer-key-only connection, so this is the node to run first when checking that a Tumblr credential is wired correctly. Tumblr wraps every response, so the payload is under data.response. The blog object is at data.response.blog.

Tumblr: Get Blog Likes

tumblr_get_blog_likes

Read the posts a blog has publicly liked. Works on a consumer-key-only connection, but ONLY for blogs that have turned on 'share likes'; a blog with likes hidden returns a 403 no matter how the request is authenticated, which is a privacy setting rather than a credential problem. Offset cannot go past 1000, and before/after/offset are mutually exclusive.

Tumblr: Get Blog Posts

tumblr_get_blog_posts

Read a blog's published posts, newest first. This is the workhorse read: watch a competitor's blog, mirror your own archive, or pull the posts behind a tag on one blog. Works on a consumer-key-only connection. Each post carries its id_string and reblog_key, which is the pair every write node needs, and note_count for engagement. Set reblog_info or notes_info to enrich the rows at the cost of a slower call.

Tumblr: Get Dashboard

tumblr_get_dashboard

Read the connected account's own dashboard: the posts from every blog it follows, newest first. The Tumblr equivalent of a home timeline, and the input to a daily digest or a keyword-watching workflow. Page with since_id to fetch only what is new since the last run, which is cheaper and more reliable than offset. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Draft Posts

tumblr_get_drafts

Read one of your blogs' unpublished drafts. Pairs with Tumblr: Create Post writing with state=draft, so an AI workflow can propose posts for a human to review in the Tumblr app rather than publishing them itself. Drafts page by before_id, not by offset. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Filtered Tags

tumblr_get_filtered_tags

List the tags the connected account has filtered out of its dashboard and search results. Read it before adding another with Tumblr: Filter Tag, because Tumblr caps the list at 1,000 tags and rejects the write that would exceed it. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Notifications

tumblr_get_notifications

Read the activity feed for one of your blogs: likes, reblogs, replies, follows, mentions, asks and answered asks, newest first. Narrow it with types to build a single-purpose monitor - a new-follower alert, or a mention watcher - instead of filtering a firehose downstream. Page with before and the server-supplied data.response._links.next. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Post

tumblr_get_post

Read ONE post in Neue Post Format: a content[] array of typed blocks plus the layout that arranges them, which is the shape Tumblr: Edit Post expects back. Use this to read a post before editing it, so the edit rewrites the real content rather than replacing it with a guess. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail. For a public read that works without OAuth, use Tumblr: Get Blog Posts with an id instead.

Tumblr: Get Post Notes

tumblr_get_post_notes

List a post's notes: who liked it, who reblogged it and who replied, each with the blog name and a timestamp. This is how engagement becomes a list of PEOPLE rather than a number, and it works on a consumer-key-only connection. Page backwards with before_timestamp taken from the oldest note on the previous page.

Tumblr: Get Queued Posts

tumblr_get_queue

Read the posts waiting in one of your blogs' queues, in the order they will publish, each with its scheduled_publish_time. The node for a workflow that tops the queue up when it runs low, or that reports on what is about to go out. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Submissions

tumblr_get_submissions

Read posts submitted to one of your blogs by other people and still awaiting moderation, including the submitter's name and email when they were not anonymous. The intake side of a community blog: route new submissions into a review queue, or alert on them. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Get Tagged Posts

tumblr_get_tagged_posts

Read posts from ACROSS Tumblr carrying one tag, newest first. This is the brand-monitoring and trend-watching node: it searches the whole network rather than one blog, and it works on a consumer-key-only connection. Page backwards with the before timestamp; there is no offset here, so a scheduled monitor should remember the newest timestamp it saw and stop when it reaches it again.

Tumblr: List Blocked Blogs

tumblr_list_blocks

List the blogs one of your blogs has blocked, at data.response.blocked_tumblelogs[]. Use it to audit a block list, or to check before blocking again. This endpoint carries its own tighter rate limit of 60 requests a minute, separate from the connector-wide budget. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: List Blog Pages

tumblr_list_blog_pages

List a blog's custom pages - the standalone About, FAQ or contact pages that sit outside the post stream - with each page's URL, title and body in one call. Works on a consumer-key-only connection. Useful for mirroring a blog's static content or checking that an About page still says what it should.

Action nodes 15

Tumblr: Block Blog

tumblr_block_blog

DESTRUCTIVE. Block another blog from one of your blogs. It immediately loses the ability to follow you, reblog you, message you or see your blog, and any existing follow is severed - unblocking does NOT restore the follow, so the relationship is gone even after Tumblr: Unblock Blog. Block by blog name, or by a post id to block whoever posted it. This endpoint carries its own limit of 60 requests a minute. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Create Post

tumblr_create_post

DESTRUCTIVE. Publish any kind of post to one of your blogs using Neue Post Format: a content[] array of typed blocks (text, image, link, audio, video, quote) plus an optional layout describing how they are arranged. This is the full surface; Tumblr: Create Text Post is the shortcut for the common case. Tumblr is a public network. A published post appears on the dashboard of every follower immediately and can be reblogged within seconds, and a reblog is an INDEPENDENT post on somebody else's blog carrying its own copy of the content. Deleting your post later removes it from your blog and from the tag feeds, but it cannot recall a reblog, cannot un-send the notification it already caused, and cannot un-fetch copies already taken. Deleting is one-way: the post cannot be restored, only written again as a new post with a new id, so anything holding the old post id or permalink points at nothing. Counts against the account's daily write budget: 250 published posts, 250 image uploads, 200 follows and 1,000 likes per day. Every request also counts against the consumer key's 1,000 per hour and 5,000 per day. Loops that write per item should pace themselves; Tumblr: Get Account Limits reports what is left. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Create Text Post

tumblr_create_text_post

DESTRUCTIVE. Publish a text post to one of your blogs from a title and a body, without assembling Neue Post Format blocks by hand: the title becomes a heading block and each blank-line-separated paragraph of the body becomes its own text block. Tumblr is a public network. A published post appears on the dashboard of every follower immediately and can be reblogged within seconds, and a reblog is an INDEPENDENT post on somebody else's blog carrying its own copy of the content. Deleting your post later removes it from your blog and from the tag feeds, but it cannot recall a reblog, cannot un-send the notification it already caused, and cannot un-fetch copies already taken. Deleting is one-way: the post cannot be restored, only written again as a new post with a new id, so anything holding the old post id or permalink points at nothing. Set state to draft or queue when a workflow should propose a post rather than publish one, which is the safe default for AI-written content. Counts against the account's daily write budget: 250 published posts, 250 image uploads, 200 follows and 1,000 likes per day. Every request also counts against the consumer key's 1,000 per hour and 5,000 per day. Loops that write per item should pace themselves; Tumblr: Get Account Limits reports what is left. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Delete Post

tumblr_delete_post

DESTRUCTIVE. Delete a post from one of your blogs. WHAT IT DOES: removes the post from your blog, from your archive and from the tag feeds. WHAT IT DOES NOT DO: recall the reblogs. Every reblog is an independent post on somebody else's blog holding its own copy of the content, and it survives your delete untouched, as do the notifications the post already sent. Deleting is one-way: the post cannot be restored, only written again as a new post with a new id, so anything holding the old post id or permalink points at nothing. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Edit Post

tumblr_edit_post

DESTRUCTIVE. Replace the content of an existing post on one of your blogs. The content array REPLACES what was there; it does not merge, so read the post with Tumblr: Get Post first and send back a modified copy rather than a partial one. Tumblr is a public network. A published post appears on the dashboard of every follower immediately and can be reblogged within seconds, and a reblog is an INDEPENDENT post on somebody else's blog carrying its own copy of the content. Deleting your post later removes it from your blog and from the tag feeds, but it cannot recall a reblog, cannot un-send the notification it already caused, and cannot un-fetch copies already taken. Editing does not reach the reblogs: every reblog of the post keeps the content it copied at the time, so a correction reaches your blog and not the copies. The previous version cannot be recovered through the API. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Filter Tag

tumblr_filter_tag

Add a tag to the connected account's filtered list, so posts carrying it stop appearing on the dashboard and in search. Private to the account, nothing is published, and the filter can be removed again in the Tumblr app - a reversible write. Tumblr caps the list at 1,000 tags, so read Tumblr: Get Filtered Tags first in a loop. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Follow Blog

tumblr_follow_blog

DESTRUCTIVE. Follow a blog as the connected account. This is a PUBLIC action: the blog is notified immediately, your account appears in its follower list, and its posts start arriving on your dashboard. Tumblr: Unfollow Blog reverses the state but cannot recall the notification, and re-following sends another one. Counts against the account's 200 follows a day, which a bulk-follow loop will exhaust quickly. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Like Post

tumblr_like_post

DESTRUCTIVE. Like somebody else's post as the connected account. This is a PUBLIC action on another person's blog: your blog name is added to that post's notes for anyone to read, and the author is notified immediately. Tumblr: Unlike Post removes the note but cannot recall the notification. Counts against the account's 1,000 likes a day. Needs the post's id AND its reblog key, both of which every read node returns. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Mute Post Notifications

tumblr_mute_post

Stop notifications from one of your own posts. Nothing is published and nobody else can tell: it is a private setting on your account, which is why this is a reversible write rather than a destructive one. The right node for a post that has gone viral and is drowning the notification feed a workflow reads. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Reblog Post

tumblr_reblog_post

DESTRUCTIVE. Reblog somebody else's post onto one of your blogs, optionally with your own commentary added underneath. Tumblr is a public network. A published post appears on the dashboard of every follower immediately and can be reblogged within seconds, and a reblog is an INDEPENDENT post on somebody else's blog carrying its own copy of the content. Deleting your post later removes it from your blog and from the tag feeds, but it cannot recall a reblog, cannot un-send the notification it already caused, and cannot un-fetch copies already taken. A reblog also notifies the original author and appears permanently in the original post's notes, and deleting your reblog later removes your copy but not that note or that notification. Needs the source post's id AND its reblog key, which every read node returns together. Counts against the account's daily write budget: 250 published posts, 250 image uploads, 200 follows and 1,000 likes per day. Every request also counts against the consumer key's 1,000 per hour and 5,000 per day. Loops that write per item should pace themselves; Tumblr: Get Account Limits reports what is left. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Reorder Queued Post

tumblr_reorder_queue

Move one queued post to a different position in a blog's queue. Nothing is published and nothing is visible to anyone until the queue reaches the post, and the move can be undone by moving it back, so this is a reversible write. Use it to promote a timely post ahead of an evergreen backlog. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Shuffle Queue

tumblr_shuffle_queue

DESTRUCTIVE. Randomize the order of every post in a blog's queue. Nothing is published by this node, so the harm is not the public kind - it is that the previous order is GONE. There is no undo and no record of what the order was, so a hand-curated sequence cannot be recovered, only rebuilt post by post with Tumblr: Reorder Queued Post. Read Tumblr: Get Queued Posts first if the order matters. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Unblock Blog

tumblr_unblock_blog

Remove a block from one of your blogs, or clear every anonymous block at once. The block itself is lifted completely, which is why this is not flagged destructive - but note it does NOT restore a follow the block severed. Skipped by the endpoint test matrix because it acts on a real third party and there is no sandbox. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Unfollow Blog

tumblr_unfollow_blog

Stop following a blog as the connected account, removing your account from its follower list and its posts from your dashboard. Reversible - following again fully restores the state - so it is not flagged destructive, but the original follow notification cannot be recalled and re-following sends a new one. Skipped by the endpoint test matrix because there is no Tumblr sandbox and the target is a real blog. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Tumblr: Unlike Post

tumblr_unlike_post

Remove the connected account's like from a post, taking your blog name back out of that post's notes. The state itself is reversible - liking again fully restores it - which is why this is not flagged destructive, but the notification the original like sent cannot be recalled, and liking again sends a new one. Skipped by the endpoint test matrix because there is no Tumblr sandbox and the target is a real person's post. Needs the full OAuth 1.0a credential (consumer key, consumer secret, token and token secret). A consumer-key-only connection can read public Tumblr but cannot run this node, and the node says so rather than sending a request that would fail.

Using the integration

On the automation canvas

Tumblr nodes chain with every other node. A schedule can drive Tumblr: Get Tagged Posts into a filter and then into a Mattering database, a form submission can become a queued post through Tumblr: Create Post, and Tumblr: Get Notifications narrowed to one event type becomes a single-purpose alert rather than a firehose you filter downstream. Two values do most of the wiring between nodes: a post's id_string and its reblog_key, which every read node returns together and which Tumblr: Like Post and Tumblr: Reblog Post both require. Use id_string rather than the numeric id, because Tumblr post ids exceed 32 bits and some JSON parsers round the numeric form; Tumblr ships the string version for exactly that reason.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. Tumblr publishes no MCP server of its own, so there is no first-party tool to defer to here; the comfortable surface to hand an agent is the 22 read nodes plus the draft-writing path. An agent can research a tag with Tumblr: Get Tagged Posts, read a blog's archive with Tumblr: Get Blog Posts, and leave a proposal in your drafts with Tumblr: Create Text Post writing with state set to draft. Keep the nine destructive nodes behind a condition or an approval task rather than in an agent's open toolset.

One credential, two modes

This is the wrinkle worth understanding once. The consumer key is enough for the public half and travels as an api_key query parameter. The full four-value credential is used to sign every request instead, with a fresh nonce and timestamp per call, and the api_key parameter is then dropped. Signing the public reads as well is not redundant: an authenticated read of somebody else's blog carries your own state on it, such as whether this account already follows the blog or already liked the post, which an unsigned read simply does not include. If a node you expect to work refuses before sending anything, that is the local OAuth gate rather than a Tumblr error, and the message names the fields to add.

Reading more than twenty rows

Every list endpoint in this API caps its limit at 20, so a workflow that wants 200 posts makes ten calls. There are three ways to walk, and picking the right one matters. Offset with limit works on most list reads, but it skips or repeats rows when the blog is posting while you page. Before and after Unix timestamps are the correct walk for a large archive on posts, likes and the tag feed, and they cannot be combined with offset. The dashboard, notifications and blocks hand back the exact parameters for the next page under data.response._links.next.query_params, so a loop should use those rather than computing its own. Tumblr: Get Dashboard additionally takes since_id, which is the right incremental read for a scheduled monitor: store the highest id_string seen and pass it back next run. Two further caps are Tumblr's: Tumblr: Get Blog Likes refuses an offset past 1000, and Tumblr: Get Draft Posts pages by before_id rather than by offset.

Publishing without surprises

Tumblr: Create Text Post is the shortcut for the common case: give it a title and a body and it assembles Neue Post Format for you, with the title as a heading block and each blank-line-separated paragraph as its own text block. Tumblr: Create Post takes the full content array when a post needs images, links, audio, video or quotes arranged deliberately, and its media blocks accept remote URLs rather than uploaded bytes, which is what an automation usually has. Both take a state, and draft or queue is the right default for anything written by a model. Tumblr: Edit Post is the node to be careful with: the content array REPLACES what was there rather than merging, so read the post with Tumblr: Get Post first and send back a modified copy, never a partial one. An edit also never reaches existing reblogs, so a correction fixes your blog and not the copies.

The nine destructive nodes, and the three that are not

Flagged destructive: Tumblr: Create Text Post, Tumblr: Create Post, Tumblr: Edit Post, Tumblr: Reblog Post, Tumblr: Delete Post, Tumblr: Like Post, Tumblr: Follow Blog, Tumblr: Block Blog and Tumblr: Shuffle Queue. Most of them carry the same reason: Tumblr is public and federated, so the action is visible immediately and a reblog of it is an independent post on somebody else's blog that your delete cannot reach. Three have a reason of their own. An edit cannot be rolled back through the API. A block severs any existing follow and unblocking does not restore it. And a shuffle publishes nothing at all, yet is still destructive, because the previous queue order is gone with no undo and no record of what it was, so a hand-curated sequence can only be rebuilt post by post. Tumblr: Unlike Post, Tumblr: Unfollow Blog and Tumblr: Unblock Blog are deliberately NOT flagged, because on Tumblr these are server-side account state and re-doing the original action genuinely restores it. The honest caveats are on those nodes anyway: the notification the first action sent cannot be recalled, re-doing sends a new one, and an unblock does not bring back a severed follow.

Reading somebody else's blog versus your own

The blog field behaves differently depending on the node, and that is deliberate. On the 19 nodes that act on YOUR blogs, it is a picker sourced from Tumblr: Get Account Info, because that endpoint returns exactly the blogs this credential can act as, which is the only correct set for a write or for a private read such as the queue, drafts, submissions, notifications or blocks. On the public read nodes it stays a free-text field, because the legitimate value there is any blog on Tumblr and Tumblr publishes no endpoint that searches or enumerates blogs. A picker offering only your own blogs on a node whose whole purpose is reading somebody else's would populate, look correct, and be useless. Each of those field descriptions spells out the accepted forms instead.

Reaching the rest of Tumblr

Four things are deliberately not built, and knowing why saves a search. Tumblr Communities is a separate product surface of membership and moderation administration acting on third parties, needing a role in the community that almost no installing account holds; it is a console rather than a workflow step. The legacy post endpoints are superseded by the Neue Post Format nodes here. Bulk blocking is one call that blocks many blogs irreversibly, where a single bad list element blocks the wrong people, so the single-block node covers the same ground one auditable step at a time. And binary media upload is deferred because Neue Post Format media blocks accept remote URLs, which covers the automation case; a workflow that produces bytes needs to host them somewhere first.

Troubleshooting

A node refuses before it sends anything, saying values are missing
That is the local OAuth gate rather than a Tumblr error, and it is working as intended. Thirty of the 37 nodes are user-scoped and need the full four-value credential; a credential holding only the consumer key runs the seven public read nodes and refuses the rest locally, naming the consumer secret, OAuth token and token secret rather than firing a request that would come back as an unexplained 401. Open Connectors, edit the Tumblr credential, and add the three values from tumblr.com/oauth/apps and api.tumblr.com/console. Nothing else in your workflows has to change.
Test Connection succeeds but says the connection is read-only
That message is the point rather than a warning to ignore. It means the saved credential holds the consumer key and nothing else, so Mattering tested the public half by reading the tag feed and is telling you which fields would unlock the other thirty nodes. A half-filled form and a deliberate read-only setup look identical in the credential list, so the test result is the only place the difference is visible. If read-only is what you intended, this is a pass.
A signed request fails with 401 Not Authorized while public reads work
Public reads use the consumer key as a query parameter, so their success says nothing about the signed half. Three things fail identically here. The token and the consumer key must belong to the SAME registered application, so a token authorized against an older application will not verify against a newer key. Both secrets must be present and untrimmed, because the consumer secret and the token secret together form the signing key and neither is ever transmitted, which means a token pasted without its secret authenticates nothing. And a stray leading or trailing space from a copy changes the signature. Re-run Test Connection: in signed mode it names the account and its blogs, so a pass also confirms you are acting as the account you meant to.
A blog's likes return 403 no matter how the request is authenticated
This is a privacy setting on that blog rather than a credential problem. Tumblr: Get Blog Likes only works for blogs that have turned on shared likes, and there is no credential or scope that overrides it. Two things do work instead. Tumblr: Get Account Likes reads the connected account's own likes whether or not that account shares them publicly. And Tumblr: Get Post Notes lists who liked a specific post, from the post's side rather than the blog's, which is often the data actually wanted.
A path like data.posts resolves to nothing
Tumblr wraps every response, success and failure alike, in an object carrying a meta block and a response block, and the connector passes that whole wrapper through. So a blog's posts are at data.response.posts[] and not at data.posts[], an account's blogs are at data.response.user.blogs[], and an error's details are at data.response.errors[]. Every sample output in the palette is modelled that way, so dragging a path from the node's own output preview always produces the correct form. One node synthesizes the wrapper rather than passing one through: Tumblr: Get Blog Avatar normalizes Tumblr's two different answers into data.response.avatar_url so a template does not have to branch on how the connection happened to be authenticated.
A loop stops writing part way through, or a request is rejected for the rate limit
Two separate ceilings can cause this and they are worth telling apart. The per-application budget is 1,000 requests an hour and 5,000 a day against the consumer key, shared across everything using that registered application, and it is far lower than Tumblr's per-IP ceiling, so it is usually the one that bites. Separately, the account has a daily write budget of 250 published posts, 250 image uploads, 200 follows and 1,000 likes, and Tumblr rejects the request that crosses the line rather than slowing down. Run Tumblr: Get Account Limits before a loop that writes and branch on what is left, and pace bulk work rather than firing it as fast as the canvas will run.
A list read returns only twenty rows
That is Tumblr's ceiling rather than a truncation on our side: every endpoint in this API caps limit at 20. Walk the rest rather than raising the number. On posts, likes and the tag feed use the before and after timestamps, which is the correct walk for an archive that is still being written to and cannot be combined with offset. On the dashboard, notifications and blocks use the parameters the server hands back at data.response._links.next.query_params. On a scheduled monitor use Tumblr: Get Dashboard with since_id, storing the highest id_string seen. Tumblr: Get Blog Likes additionally refuses an offset past 1000, so an archive of likes has to be walked by timestamp.
A post was published that should have stayed internal
Act on the reblogs rather than only on the post. Tumblr: Delete Post removes the post from your blog, your archive and the tag feeds, and it is one-way: the post cannot be restored, only written again as a new post with a new id, so anything holding the old permalink then points at nothing. What it cannot do is recall a reblog, because each one is an independent post on somebody else's blog holding its own copy, and it cannot un-send the notification the post already caused. Tumblr: Get Post Notes shows who reblogged it, which is the only route to those copies and it is a human one. To prevent a repeat, set the post state to draft or queue on Tumblr: Create Text Post and Tumblr: Create Post and gate the publishing step behind an approval task.
The queue is in the wrong order after a workflow ran
Check whether Tumblr: Shuffle Queue was in the path. It publishes nothing, which is why it can look harmless, but it randomizes the whole queue and the previous order is gone with no undo and no record of what it was. The only rebuild is post by post with Tumblr: Reorder Queued Post, reading the current state from Tumblr: Get Queued Posts. If order matters on a blog, read the queue into a Mattering database on a schedule so there is something to rebuild from, and keep the shuffle node out of any automation an agent can reach.

Tumblr is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products