Destination Presets

What destination presets are for

A preset is a reusable "where does this go" configuration. You pick up to 12 channels (platforms + accounts), optionally define per-channel caption overrides, hashtags, and UTM parameters, then save it as a preset. When composing a post, apply the preset and the composer pre-fills your channel picker — you see a preview of how each channel's version looks before publishing.

Useful when you have consistent distribution patterns (personal + company LinkedIn, your 3 main TikTok accounts) or when an agency needs every post to land on multiple client workspaces with client-specific captions.

Where it lives

Open Automation → Destination Presets in the sidebar (/automation?tab=presets), or use the composer's preset picker when drafting.

Plan availability

The 12-channel cap is enforced at the DB CHECK, the Zod schema, and the UI, so a preset can never target more channels than realistic.

Step 1 — Create a preset

1. Open /automation?tab=presets.
2. Click New preset.
3. Name — e.g. "Personal + Company LinkedIn".
4. Channels — add up to 12. Each channel is a platform + connected account.
5. Per-channel tweaks (optional) — click a channel row to add:
   • Caption override (supports {{variables}} like post signatures)
   • Hashtag override
   • UTM source/medium/campaign (for analytics tracking on external links)
6. Click Save.

The preset is now available in the composer's preset picker.

Step 2 — Apply a preset in the composer

1. Open the composer and write your post.
2. In the channel picker, click Load preset and choose your preset.
3. The composer pre-fills all channels from the preset and shows per-channel previews.
4. Review the preview — each channel renders its destination-specific caption, hashtags, and UTM parameters.
5. Publish or schedule normally.

If you want to tweak the selection, remove or add channels individually; the preset is just a starting point.

Step 3 — Preview before publishing

The preview endpoint shows exactly how each channel's version looks:

1. On the preset detail, click Preview with sample post.
2. Aidelly evaluates all 12 channels with the preset's transforms applied.
3. Skipped or incompatible channels show the skip reason inline.

Useful to verify a video-only preset won't try to publish a text-only post to a text-only channel.

What gets skipped (and why)

The preview marks channels the source post can't publish to instead of failing: a video-only channel (YouTube Shorts) with a text or image post, an image-only channel (Pinterest) with a video, and similar format mismatches. Fix the media or drop the channel before scheduling.

Presets are workspace-scoped — a preset targets connected accounts inside its own workspace, and workspace-membership rules gate who can create or apply one.

How presets interact with other Aidelly features

• Queues — presets answer where, queues answer when. Apply a preset while composing, then drop the post into a queue for recurring timing.
• Content Automations — an automation rule can point its generated content at a preset, so every generated post targets the same channels.
• Calendar — posts composed with a preset carry a preset badge on their calendar event detail.

Per-channel transforms, explained

Each channel in a preset can have independent overrides:

• Caption — inherit the source caption or replace it with a template. Templates support {{title}}, {{caption}}, and {{link}} variables, resolved per channel at preview time.
• Hashtags — swap in a platform-specific hashtag set (Instagram gets one set, TikTok another).
• UTM parameters — appended to outbound links so your analytics can attribute traffic per channel.
• Time offset — stagger a channel's copy by minutes/hours relative to the source post.

Plan limits + cap rationale

The 12-channel cap matches the realistic ceiling: 11 supported platforms + 1 backup workspace. Anything beyond that is usually a sign of a misconfigured preset (e.g. "post to every account" anti-pattern that floods feeds).

Troubleshooting

• A channel in the preset isn't receiving publishes — check the account is connected, and the preset is selecting the right account (workspace + platform).
• Caption variables aren't substituting — variables are resolved at compose time per channel. If a destination workspace is missing the variable, the literal {{name}} text stays in place.
• Per-channel UTM tags aren't showing up — UTM parameters are appended to links in the caption. If the preset doesn't have a UTM override, links remain untagged.
• Member can't see a preset — they need read access to the destination workspace. Check workspace_memberships for that user.