Repository navigation
Links
- Import links from a CSV file or a Flared export, in the app, the API (
POST /v1/links/import), or MCP. - iPhone and Android destinations: send phone visitors to an app link instead of the destination.
- A UTM builder in the link form.
- The links list is easier to search and act on, the short link shows before you create it, and link details and analytics are simpler.
- Daily clicks switch between a chart and a table.
- The MCP tool
export_links.
Webhooks and automations
- Webhooks send a signed POST when a link is created, changed, turned off or on, or reaches a click milestone. The owner manages them in Settings → Webhooks. See webhooks.md.
- Automations run actions on a link when a trigger happens, including when the destination stops loading. An automation can send a webhook. See automations.md.
- New limits in Settings → Limits and usage: 10 webhook endpoints and 25 automations by default. A limit of 0 turns the feature off.
Look and feel
- A new look across the app: Figtree text, the pixel link mark, new colours and controls, and a phone layout with a bottom tab bar and sheets.
- Settings is split into Account and Workspace sections.
- Connections lists connected apps apart from AI assistants.
- Dialogs, menus, and the side panel open and close smoothly.
Upgrade
Most copies upgrade with a clean pull request. A copy whose Cloudflare resources Deploy renamed, such as a second copy in one account with queues named flared-clicks-2, gets an issue that names wrangler.jsonc this one time. Merge by hand as the issue shows, and in wrangler.jsonc keep your own Worker, database, and queue names and IDs, and take "max_batch_size": 3 for the click queue with its comment. From 0.2.0 on, the upgrade workflow does this itself; see upgrade.md.
Fixes
- The click queue takes at most 3 clicks per run, so one run stays within the 50 D1 queries of Workers Free.
- The upgrade workflow takes a release's
wrangler.jsoncwith your copy's own names and IDs when the release changes lines next to them, and opens an issue only when you changed something else in that file.
Recovery
- Changing
AUTH_SECRET, or setting it on an installation that ran without it, changes every webhook endpoint secret. See recovery.md.
Database changes
packages/data/migrations/analytics/0006_click_milestones.sqlpackages/data/migrations/identity/0020_webhook_limits.sqlpackages/data/migrations/identity/0021_automation_limits.sqlpackages/data/migrations/identity/0022_operator_oauth_clients.sqlpackages/data/migrations/routing/0007_device_destinations.sqlpackages/data/migrations/routing/0008_webhooks.sqlpackages/data/migrations/routing/0009_automations.sqlpackages/data/migrations/routing/0010_transports.sqlpackages/data/migrations/routing/0011_click_forwarding.sqlpackages/data/migrations/routing/0012_hooks.sql
Each one only adds tables or columns. bun run deploy applies them before it deploys the Worker. No new secrets or settings are needed.