Publishes to Dev.to
Publish to Dev.to alongside your own blog.
A second surface for the same work: articles go to Dev.to through its API with a cover image and up to four tags, published or held as drafts.
One project and three articles free. No card required.
What you connect
authorise once, publish from then onA Dev.to API key
What publishing to Dev.to does
Articles, tagged and covered
Each piece arrives with its title, body, cover image and up to four tags — the shape Dev.to distributes to its feeds.
Unpublishing is reversible
Taking an article down flips it back to an unpublished draft on Dev.to rather than deleting it.
True of every integration
A full article, not a paste job
Each publish carries the title, slug, body, meta description, tags and the generated banner image. Nothing is reformatted by hand afterwards.
Republishing updates in place
The post’s id in your platform is stored on first publish. Publishing the article again updates that post instead of creating a duplicate.
Test before anything ships
Every connection has a test call that verifies the credentials against the platform before an article is ever sent. Your agent can run it too: test_integration.
A log per publish
Every attempt is recorded with its outcome. Failures can be retried without regenerating anything — retry_publish picks up the same article.
The shape of it
One project and three articles free. No card required.