Mattering Automations DEV Community integration
Connect DEV Community (dev.to) to Mattering Automations: the public article feed with filters and search, your drafts and published posts, article create and update with the publish switch, threaded comments, followers, tags, reading list, and organizations as workflow steps, authenticated with one free API key.
The Mattering Automations DEV Community integration adds the Forem API v1 that powers dev.to to your automation canvas: read the public article feed with tag, author, freshness, and top-N-days filters, list the platform chronologically, search articles by title, tag, and body content, list your own published and draft articles, create and update articles with publishing riding the published flag, read threaded comment trees, list your followers and followed tags, export your reading list, and read the platform's tags, organizations, podcast episodes, and video articles.
The credential is a single API key generated in your dev.to account settings and sent as the api-key header on every request. DEV accounts and API keys are free, the key is unscoped and acts as the user it belongs to, and setup takes a few minutes: generate the key, paste it into a Mattering credential, and test the connection. This guide walks through each step and ends with the full node reference.
The safety modeling is stated on the nodes rather than buried. Of the 25 nodes, 22 read and 3 act. The two article writes, DEV Community: Create Article and DEV Community: Update Article, are reversible: setting published to false on an update reverts a live article to draft. One node carries a destructive flag even though it deletes nothing: DEV Community: Follow Users or Organizations, because the public API has no unfollow endpoint, so a follow made by an automation persists until undone by hand. The public API also has no article delete at all, and the admin and moderator surface, including user lookup by email, organization management, and the dedicated unpublish route, is deliberately not shipped.
Before you start
- A DEV Community account at dev.to. Accounts are free, and the API key is generated from account settings with no approval step.
- A Mattering workspace with access to the Automations app.
- A deliberate choice of which DEV account the automation acts as: the key is unscoped and everything it does, publishing, saving, following, happens as that user. For experiments, a dedicated test account keeps API-created drafts out of your main profile, because the public API has no way to delete them.
Generate a DEV Community API key
Mattering authenticates to DEV with a single API key sent as the api-key header on every request. There are no permission scopes to choose: the key acts as the user it belongs to, which makes generating it quick and choosing the account it belongs to the only real decision.
Connect DEV Community to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a DEV Community section should list the query and action nodes. Drop DEV Community: Get My User onto the canvas and run a test step. It is the integration's credential probe: a healthy key returns the account's id, username, name, and follower count, and a bad one returns 401. It matters that you verify with this node specifically, because several DEV read endpoints are documented as public: the feed, tags, and organization nodes can return data even when the credential is broken, so only an authenticated node proves the key.
Next, run DEV Community: List My Articles (All) and note an article ID, because that is the ID universe DEV Community: Update Article accepts: the API only lets a key update articles its own user authored. Then run DEV Community: List Tags for the tag names that feed the article filter and article writes. Everything in this verify path is read-only: it cannot publish, follow, or change anything, so it is safe to re-run whenever you rotate the key.
Node reference
25 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 22
DEV Community: Get Article
devto_get_article
Fetch one published article by its numeric ID: the complete article object including its HTML and Markdown body, tags, and author profile.
DEV Community: Get Article by Path
devto_get_article_by_path
Fetch one published article by its URL path parts - the author (or organization) username and the article slug - resolving a dev.to article URL straight into its API object.
DEV Community: Get Comment
devto_get_comment
Fetch one comment and all of its nested descendant replies by the comment's alphanumeric id_code.
DEV Community: Get My User
devto_get_me
Fetch the user the API key belongs to: id, username, name, profile links, badge ids, and follower count. Requires a valid key (a bad one returns 401), so this is the credential health check to run first in any DEV automation.
DEV Community: Get Organization
devto_get_organization
Fetch one organization's full public profile by slug (username) or numeric id: name, summary, tech stack, tagline, story, links, and joined date.
DEV Community: Get User
devto_get_user
Fetch a single user's public profile by numeric ID: name, summary, social handles, location, and profile image. The API reference says a username works in the same field, but on dev.to a username here returns 404 (live-verified 2026-08-11) - pass the numeric id, which follower and article payloads carry.
DEV Community: List Articles
devto_list_articles
List published articles from the public feed - by default featured articles ordered by descending popularity. Filter by tag(s), author or organization username, freshness state, a top-N-days popularity window, or a series (collection). Returns article ids, titles, URLs, tags, reaction and comment counts, and author profiles.
DEV Community: List Comments
devto_list_comments
List the comments on an article (a_id) or podcast episode (p_id) as threaded conversations - each top-level comment carries its replies nested recursively in children. Fill exactly one of a_id or p_id. Omit page to get the full tree in one payload; with page, pagination applies to top-level comments only.
DEV Community: List Followed Tags
devto_list_followed_tags
List the tags the authenticated user follows, each with its tag id, name, and the user's interest points for it.
DEV Community: List Latest Articles
devto_list_latest_articles
List published articles ordered strictly by descending publication date, bypassing the feed's popularity ranking - the endpoint for chronological timelines and latest-posts monitoring.
DEV Community: List My Articles (All)
devto_list_my_all_articles
List ALL of the authenticated user's articles - unpublished drafts first (reverse creation order), then published articles (reverse publication order). This is the full editable universe, and the source the Update Article picker draws from.
DEV Community: List My Followers
devto_list_followers
List the users who follow the authenticated user, with each follower's user_id, name, profile path, and image - the read behind follower-growth tracking and new-follower notifications.
DEV Community: List My Published Articles
devto_list_my_published_articles
List the authenticated user's PUBLISHED articles in reverse chronological publication order - the honest source for 'my live posts' dashboards and cross-posting automations.
DEV Community: List My Unpublished Articles
devto_list_my_unpublished_articles
List the authenticated user's DRAFT (unpublished) articles in reverse chronological creation order - the queue a publish-on-schedule automation drains.
DEV Community: List Organization Articles
devto_list_organization_articles
List an organization's published articles (by username or numeric id) in reverse chronological publication order - the feed behind a company-blog mirror or digest.
DEV Community: List Organization Users
devto_list_organization_users
List the public member profiles of an organization (by username or numeric id) - team directory reads for org pages and mention lists.
DEV Community: List Organizations
devto_list_organizations
List the platform's organizations as compact rows: numeric id, name, slug, summary, tagline, profile image, and URL (the list rows are thinner than the single-org get). The slug from here feeds the organization get/users/articles nodes.
DEV Community: List Podcast Episodes
devto_list_podcast_episodes
List published podcast episodes in reverse chronological order, optionally filtered to one podcast by its slug. Episode ids here are the p_id the List Comments node takes.
DEV Community: List Reading List
devto_list_reading_list
List the articles saved to the authenticated user's reading list (the posts they reacted to with save), as standard article objects - read-it-later export and digest automations start here.
DEV Community: List Tags
devto_list_tags
List the platform's tags ordered by popularity, with each tag's id, name, and colors. The tag names feed the List Articles tag filter and article-write tags.
DEV Community: List Video Articles
devto_list_videos
List published articles that carry an uploaded video, ordered by descending popularity, with each video's duration, source URL, and thumbnail.
DEV Community: Search Articles
devto_search_articles
Search published articles: the query matches against titles, tags, and body content, optionally restricted to articles published in the last N days.
Action nodes 3
DEV Community: Create Article
devto_create_article
Create an article - as a draft by default, or live immediately with published=true. Publishing is reversible (DEV Community: Update Article with published=false reverts it to draft), but note the public API has no article DELETE: a created draft persists until removed by hand in the DEV dashboard. Returns 201 with the article; 422 with an error message on validation failures.
DEV Community: Follow Users or Organizations
devto_follow
NO API UNDO: follow users and/or organizations in bulk on behalf of the authenticated user. Nothing is deleted, but the public API has no unfollow endpoint, so every follow made here persists until undone by hand in the DEV UI - treat it like an irreversible action in automations and never run it in a blind test.
DEV Community: Update Article
devto_update_article
Update one of YOUR articles (the key must belong to the author); only the fields you fill are sent. This node is also the publish/unpublish switch: published=true takes a draft live, published=false reverts a live article to draft (the docs' supported author-side unpublish - the dedicated unpublish endpoint is moderator-only).
Using the integration
On the automation canvas
DEV Community nodes chain with every other node: a CMS webhook can run DEV Community: Create Article to mirror a post as a draft and then open a review task in Mattering Productivity, a scheduled sweep can run DEV Community: Search Articles for a topic and write new matches into a Mattering database, and DEV Community: List My Followers can feed a weekly growth snapshot. Listers return plain arrays, so downstream paths look like data[].id and data[].title, and pagination is page and per_page until a short page comes back.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can check what already exists with DEV Community: Search Articles, draft a post with DEV Community: Create Article, and take it live later with DEV Community: Update Article. The read nodes are the safest surface to hand an agent; keep the publish flip and the follow node behind conditions or approval steps.
Publishing, unpublishing, and the missing delete
DEV Community: Create Article takes the title, Markdown body, tags, series, cover image, canonical URL, and an organization id, and creates a draft unless published is set to true. DEV Community: Update Article sends only the fields you fill and doubles as the publish switch: published true takes a draft live, published false reverts a live article to draft, which is the documented author-side unpublish, since the dedicated unpublish endpoint requires a moderator role. What does not exist is delete: the public API supports reading and updating articles but not removing them, so cleanup of unwanted drafts is a manual dashboard action.
Cross-posting done right
The canonical_url field on the article writes is the piece that makes DEV mirroring safe for your own site's search standing: set it to the original post's URL and DEV's copy points search engines at the source. The honest pattern is webhook from your CMS, DEV Community: Create Article as a draft with canonical_url filled, a human review task, then DEV Community: Update Article to publish. DEV Community: Get Article by Path closes the loop from the other direction, resolving a dev.to URL into its API object when a workflow starts from a link.
Monitoring feeds, tags, and comments
DEV Community: List Articles reads the public feed with filters for a tag, comma-separated tag lists to include or exclude, an author or organization username, a freshness state, a top-N-days popularity window, or a series. DEV Community: List Latest Articles bypasses the popularity ranking for strict reverse-chronological monitoring, and DEV Community: List Comments returns an article's threads with replies nested recursively in children when you pass its a_id. Comment ids in those trees are alphanumeric id_codes, which is what DEV Community: Get Comment takes.
The follow node, gated
DEV Community: Follow Users or Organizations follows users and organizations in bulk on behalf of the authenticated account, and it is the integration's one destructive-flagged node for a reason that has nothing to do with deletion: the public API has no unfollow endpoint, so every follow it makes persists until a person undoes it in the DEV interface. Treat it like an irreversible action: keep it behind an approval task or a manual run, never a bare trigger, and never point it at a list an automation assembled without review.
What is deliberately not included
The documented Forem surface is larger than this integration, and the gaps are chosen, not missed. Admin and moderator endpoints are out: user lookup by email, organization create, update, and delete, user moderation, and the dedicated unpublish route, which the docs restrict to admin and moderator roles that API users on dev.to do not hold. The reactions toggle is out because its removal semantics are a toggle rather than a clean undo. And the integration targets dev.to specifically: other Forem communities run on their own hosts and are out of scope.
Troubleshooting
Test Connection fails with 401 unauthorized
Public feed nodes return data but my-articles, reading list, or follower nodes return 401
DEV Community: Update Article fails on an article ID that DEV Community: Get Article reads fine
DEV Community: Create Article returns 422
DEV Community: List Comments errors or returns nothing
DEV Community: Get Comment returns 404 for a comment you can see on the site
Nodes start returning 429 during a large sweep
An automation followed accounts it should not have
Related
The DEV Community MCP
What connecting DEV Community unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
DEV Community 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.