Define a route once — source account, up to 12 destinations across any platform, account, or workspace — and every publish from that source fans out automatically. Built for creators with parallel audiences and agencies running clients at scale.
Pick from 11 platforms, any connected account, and any workspace you have access to.
Route a single publish to multiple client workspaces — agency-only.
Incompatible destinations are skipped with a logged reason, not silently dropped.
Composer, chat, API, MCP agents, RSS auto-post, repurpose — same fanout rules apply.
Override the caption per destination so each platform reads native.
Every scheduled post shows which route created it — easy to audit and undo.
Members can only target workspaces they have access to. Route edits respect roles.
Preview exactly which destinations a sample publish would hit before flipping the route on.
Find the routes manager under Automation in the sidebar. Click "New route".
A primary account (e.g. your LinkedIn personal page) or "any publish in this workspace".
Mix platforms, accounts, and workspaces. Each destination can have its own caption tweak.
Composer, chat, API, agents, RSS auto-post — any path. The route fans the publish out automatically.
A saved fanout rule. You define a source — usually a primary account like your main LinkedIn — and up to 12 destinations across any platform, account, or workspace. When a post publishes on the source, Aidelly automatically schedules matching copies on every destination.
The composer is a per-post choice; routes are persistent rules. Pick the platforms once on the route, and every subsequent publish from the source flows out automatically — including from chat, agents, RSS auto-post, repurpose, the API, and any other surface that creates a post. You stop thinking about distribution.
A video-only route applied to a text-only post (or a photo route applied to a video) is skipped, not failed. The skip is recorded as a scheduled_post_events row so you can see exactly which destinations were excluded and why — visible on the post detail and in the activity log.
Hard-capped at 12 at the DB CHECK, Zod schema, and UI layers. That cap covers every realistic workflow — 11 supported platforms plus a backup workspace — without letting a runaway route blow up your AI credit consumption.
Yes. Agency plans can route a publish in one client workspace to another (e.g. a holding workspace + 5 client workspaces), so internal posts can land on every brand at once. Member-scope permissions are honored — a member can only target workspaces they have access to.
Routes are evaluated at publish time, so editing a route only affects future publishes. In-flight scheduled posts keep the destination set they were created with — visible on the calendar with a route badge per post.
One route. One publish. Every destination, every time.