How dlvr.it's Auto-Sharing Workflow Works

Updated

dlvr.it's auto-sharing workflow is a three-step setup: connect a content source (RSS, Instagram, Facebook, or TikTok), choose what types of content to share (photos, links, or videos), and connect your social accounts as outputs. After that, whenever the source publishes something new, dlvr.it automatically shares it to the connected channels. The setup is designed to be completed in seconds, and once configured, the workflow runs without manual posting.

Step 1: Connect your content input

The workflow starts with a source that dlvr.it monitors for new content. According to the site, supported inputs include:

  • RSS feeds — useful for blogs, news sites, and any site that publishes a feed
  • Instagram profiles
  • Facebook pages
  • TikTok

You connect one of these as the "input." This is the origin point of the automation: dlvr.it watches it, and anything new that appears there becomes a candidate for sharing.

What to expect: once the input is connected, dlvr.it treats new items from that source as triggers. You don't need to copy links or re-upload media manually.

Step 2: Choose what to auto-share

Next, you tell dlvr.it which content types from that input should be distributed. The site lists these options:

Content type What dlvr.it does with it
Photos Auto resized and formatted for each platform
Links Shares breaking news and blog posts instantly
Videos Repurposes video content across social channels
Reels & Shorts Native video uploads to maximize organic reach
Carousels Distributes multi-image posts

Selecting content types keeps the automation focused — for example, you can share only links from an RSS feed and skip images, or share photos and videos from an Instagram profile. The platform handles formatting differences between networks, such as resizing photos per platform.

Step 3: Connect your social accounts as outputs

The final step is connecting the destination accounts. dlvr.it states it supports 21 social platforms, including Facebook, Twitter, LinkedIn, Pinterest, TikTok, Instagram, Threads, Bluesky, and Google Business Profile. Each connected account becomes an "output."

What to expect: after outputs are connected, the rule is live. When there's a new post on your input, dlvr.it automatically shares it to your outputs — this is the core loop the site describes as "Post once. Share everywhere."

What happens after setup

Once all three steps are complete, the workflow runs on its own:

  1. A new item appears at your input (a new RSS item, Instagram post, Facebook page post, or TikTok video).
  2. dlvr.it picks it up automatically.
  3. The item is shared to every connected output channel, formatted for each platform.

The site reports scale figures that indicate this is a mature automation pipeline: 1.5M social channels managed and 5M posts processed daily. For a single user, the practical takeaway is that the same input-to-output loop handles both occasional posting and high-volume publishing.

Where the workflow fits — and where it doesn't

Good fit: you already publish to one place (a blog with an RSS feed, an Instagram profile, a Facebook page) and want that content mirrored to multiple networks without repeating the upload each time. The three-step model means the effort is front-loaded into setup, not ongoing posting.

Check before committing: the site's feature pages cover platform-specific auto-posting (Facebook, Instagram, Twitter, Bluesky, Threads, Pinterest, TikTok, Google Business Profile), so confirm your specific destination networks are among the 21 supported. Pricing details are listed on the site's Pricing page; review that page for current plan terms rather than assuming a free tier.

Common snag to plan for: the automation shares whatever appears at the input, so content type selection in Step 2 is your main control over what gets distributed. Decide deliberately whether links, photos, and videos should all flow through, or only some of them.

To start, use the site's "Start Auto Posting" entry point, complete the three connections, and verify with one test post at the source to confirm it reaches your outputs as expected.