Short Menu

Create and manage branded short links through Short Menu, the shortener and link-analytics service from Appiculous. Agents attach a measurable link to every outbound message.

3 actions API key available

Short Menu website ↗ Platform Documentation ↗ Capability data verified 2026-08-01

A CMS publish event retires a landing page and replaces it with a new URL

Agent reads the retired URL and its replacement from the publish payload

Agent looks up its own link register for the short links it minted against the retired URL, because Short Menu publishes no listing endpoint

Agent confirms the replacement page is live and belongs to the same campaign the link was created for

Agent posts each affected short URL, where that link was distributed, and the destination it is about to be given

The campaign owner approves the repoint, and only then does the agent call Update Short Link

What This Integration Enables

Short Menu, from Appiculous, is a deliberately small surface, and this page is not going to pretend otherwise. The connector exposes three operations: create a link, update it, delete it. There is no listing endpoint, no analytics endpoint and no webhook, and the vendor describes the API as in active development. What you get instead is the one property that makes a short link worth anything in the first place. The slug and the domain are fixed at creation, so the short URL is a permanent public address, and the destination behind it is yours to change forever.

That constraint decides how you build with it. Because there is no way to ask Short Menu what links exist, the flow that creates a link has to be the system of record. An agent calls Create Short Link, gets back the identifier, the full short URL and the destination page title, and writes all of that to the row, ticket or record that caused the link to exist. From then on the register, not the shortener, is what tells you which link was printed on which flyer and which campaign owns it. That is more discipline than a bigger connector demands, and it is also more useful, because the register lives next to the campaign rather than in a separate tool nobody opens. Links are created on the shared shm.to domain by default, or on any custom domain configured on the account, and tags are matched by name and reused automatically so campaign grouping stays consistent without a lookup step.

Without FlowRunner

The short URL and the page share a fate When a landing page moves, every copy of the link already printed or sent points at nothing

Nobody knows which links exist Links are created ad hoc and the only record of them is whoever made them

Repointing is a manual errand Someone opens the shortener, finds the link by memory, and edits the destination

With FlowRunner

The address outlives the page The short URL stays constant and the destination behind it is updated in place

The workflow holds the register Every link the agent mints is written back to a record with its ID, campaign and where it was distributed

Repointing is a reviewed step The proposed new destination is shown to the owner before any live link changes

Use Case Scenarios

The landing page moves and the flyer does not

A campaign page in WordPress is retired and replaced. The agent reads the change, looks up the register it has been keeping in Airtable for links minted against the old URL, and finds three, one of which is on a printed flyer that went out to a mailing list last month. It calls Update Short Link on each one after the owner signs off. The short URLs never change, so the flyer keeps working and nobody reprints anything.

A trackable link on every publish

When a release note, blog post or product page goes live, the agent calls Create Short Link with a memorable slug derived from the title and a tag naming the campaign. Short Menu returns the identifier, the short URL and the destination page title where it could read one, and the agent writes all three back to the content record and posts the link to the team channel in Slack. Every published item leaves with a measurable address attached, without anyone opening the shortener.

Client work, tagged so the reporting survives the handover

An agency mints links per client and per channel, tagging each one by client name at creation. Because tags are matched by name and reused, the same tag string keeps resolving to the same grouping across months and across whoever built the flow. When a client relationship ends, the agent proposes the cleanup set from its register and asks before deleting anything, because deletion here takes the click history with it.

Human-in-Loop Highlight

On most connectors the dangerous operation is the delete. Here the dangerous operation is the edit. Update Short Link is the only thing you can change about a live Short Menu link, since the slug and the domain are locked at creation, and the moment it runs, every copy of that short URL in the world starts going somewhere new. That includes the copies you cannot reach: the flyer already in the post, the QR code already on a poster, the link already sitting in someone's saved messages. So the agent never repoints on its own. When a destination moves it assembles the case first, pulling from its own register the short URL, the campaign that owns it, and every place that link is known to have been distributed, then asks one question in Slack: "shm.to/spring25 is printed on the March mailer and currently points at the retired offer page. Repoint it to the new offer, or leave it and let it 404?" A person answers. Delete Short Link sits behind the same gate for a harder reason, because it is permanent, the URL stops resolving for everyone, and the click history goes with it. FlowRunner treats both as automation exceptions: the agent finds the links, works out the blast radius, and stops for a person at the step that reaches an audience it cannot recall.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

3 actions

Short Links

Create Short Link Creates a link that redirects to a destination URL, on the shared shm.to domain by default or on any custom domain configured on the account. The slug can be supplied to produce a memorable branded link or omitted for a generated one, and either way it must be unique within the domain. Tags are matched by name and reused when they already exist. Returns the identifier, the full short URL and the destination page title where Short Menu could read one, which is what a workflow writes back into its own register.
Update Short Link Repoints an existing link at a new destination without changing the short URL people have already shared, and replaces its tag list. Only the destination and the tags can be changed, because the slug and domain are fixed at creation. Fields left empty keep their current values, so tags survive a destination only edit. Used whenever a page moves and the link is already in circulation, and always after a person has approved the new target.
Delete Short Link Permanently deletes a link. The short URL stops resolving and anyone following it no longer reaches the destination, and the recorded click history is removed along with it. Update Short Link is the right call whenever a link is already in circulation and only needs pointing somewhere else. Used at genuine end of life, behind a human decision.

Frequently Asked Questions

What can FlowRunner do with Short Menu?

FlowRunner agents can run Create Short Link, Update Short Link, and Delete Short Link in Short Menu.

Does connecting Short Menu to FlowRunner require OAuth?

No. Short Menu connects to FlowRunner with an API key, no OAuth flow required.

Can Short Menu trigger a FlowRunner workflow automatically?

Short Menu doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Short Menu

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us