dlvr.it
Social MediaConnect AI agents to dlvr.it, a social media automation service that publishes content from feeds. Agents publish to connected accounts and read the publishing routes and account state behind each one.
What This Integration Enables
dlvr.it is built around one idea that most social tools abandoned: a route. A route is a source-to-destination pipeline that somebody configured once, with its own set of social destinations, its own content filters, and its own formatting rules, and it keeps running long after the person who built it stopped thinking about it. That design is genuinely useful, because it means the distribution policy lives in one place instead of being rebuilt in every campaign. It also means the connector's job is not to reinvent that policy. Post to Route publishes a message through a route and lets the route decide where it lands and how it looks. Post to Account bypasses route automation entirely and publishes to exactly one connected social account. Both support attaching media by URL, appending a trackable shared link, and deferring the post into a queue at a chosen time and position.
Two facts about this connector's actual surface should shape every flow built on it, and both are the kind of thing that is cheaper to know now than to discover in production. First, routes are read-only here. There is no Create Route and no Update Route, because dlvr.it configures routes in its own interface. An agent can use a route and cannot build, repair, or narrow one. Second, List Routes returns each route's id and name and nothing else. The destinations behind a route, the filters it applies, and the formatting it imposes are not exposed to the flow. So a flow calling Post to Route is deliberately handing a message to a distribution policy it cannot read. That is a reasonable trade when a person set the route up on purpose, and it is exactly why the approval gate on this connector belongs on the choice of route rather than on the wording of the post. There are no triggers either, since dlvr.it publishes no event subscription, so a flow starts from a schedule or from another system rather than from anything dlvr.it pushes.
Without FlowRunner
With FlowRunner
Use Case Scenarios
New content distributed through a route somebody already trusts
An article publishes on the company blog. Rather than rebuilding the distribution list in the flow, an agent calls List Routes, matches the route named for that content category, and calls Shorten URL on the article link so the click data lands in dlvr.it's own reporting. It then calls Post to Route with the message, the short link attached through Attach Shared Link, and Add to Queue enabled with a Queue Position of Last, so the post enters the route's social queue behind whatever is already scheduled rather than jumping the line. The route applies its own destinations and formatting. The flow supplied the content and the timing, and left the policy where the policy already lived.
A single-network correction that must not fan out
A pricing figure in a published post is wrong. The correction needs to go to LinkedIn, where the original was seen by the audience that matters, and nowhere else. Running the correction back through the route would republish it to every destination the route feeds, which is the opposite of a quiet fix. So the agent calls List Accounts, finds the LinkedIn account by its network and public profile URL, and calls Post to Account with the corrected message. Same connector, deliberately narrower blast radius. The existence of two publishing actions with different reach is the useful part of this integration, and choosing between them is a real decision rather than a stylistic one.
An evergreen queue that fills itself
A content library in Notion holds evergreen posts tagged by topic. Twice a week a scheduled flow selects the least recently distributed item, calls Shorten URL on its link, and calls Post to Route with Add to Queue enabled, Scheduled Time set to the next open slot, and Queue Position set to Last. The route handles the network-specific formatting. The flow updates the library record with the distribution date so the same item does not resurface for months. Nobody sits down on Monday to fill a queue, and the library stays the single source of what has gone out.
Human-in-Loop Highlight
Post to Route is a one-line call with a blast radius the flow cannot measure. List Routes returns an id and a name, and that is the entire picture the connector gets: the destinations behind the route, the filters it applies, and the formatting it imposes are configured in dlvr.it and never surface in the response. There is no Create Route or Update Route here either, so an agent that guesses wrong cannot narrow the route and try again. It has already published. So on any distribution that is corrective, sensitive, or off the normal calendar, the agent assembles what it can actually see and stops. It sends the distribution owner a message with the route name it matched, the full connected account inventory from List Accounts including each network and public profile URL, and the drafted message: "Ready to send this correction. Matched route 'Blog to Social' by name. This connector cannot read which of the 9 connected accounts that route feeds. Send through the route, or send to LinkedIn only with Post to Account?" The person answering knows what the route contains. The agent knows that it does not, and says so rather than proceeding on a name match.
Agent Capabilities
5 actionsRoutes and Accounts
2- List Routes Retrieves every automation route configured on the connected dlvr.it account. A route is a source-to-destination pipeline, and the returned route ids are the target for Post to Route. The response carries the route's id and name, not the destinations behind it, so treat a route as a named policy rather than as a readable list.
- List Accounts Retrieves every connected social account, including its network and public profile URL. The returned account ids are the target for Post to Account. This is the action that tells a flow exactly which surfaces the dlvr.it connection can reach.
Publishing
3- Post to Route Publishes a message through a route, applying that route's configured social destinations, filters, and formatting. Supports attaching media by URL, appending a trackable shared link, and deferring the post into the route's social queue at a scheduled time and position. The widest-reach action in this connector, and the one whose reach the flow cannot inspect.
- Post to Account Publishes a message directly to a single connected social account, bypassing route-level automation. Supports the same media, shared-link, and queue options as Post to Route. Use it when the correct blast radius is exactly one network and nothing else.
- Shorten URL Generates a dlvr.it short URL for a long link using the account's configured shortener, so distributed links are trackable without anyone remembering to shorten them by hand. Available to paid dlvr.it subscribers only.
Frequently Asked Questions
What can FlowRunner do with dlvr.it?
FlowRunner agents can run List Routes, List Accounts, and Post to Route in dlvr.it, plus 2 more actions.
Does connecting dlvr.it to FlowRunner require OAuth?
No. dlvr.it connects to FlowRunner with an API key, no OAuth flow required.
Can dlvr.it trigger a FlowRunner workflow automatically?
dlvr.it doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with dlvr.it
$100 in credits. No card required. Connect in minutes.