Does moving a Shortcut story update the Trello card?

Not in this create-only flow. To mirror state you'd add an update step keyed on the stored story ID that moves the card with move_card when the Shortcut state changes.

How does it avoid duplicate cards?

By storing the Shortcut story ID next to the Trello card ID it created. Each run lists current stories, drops ones already mapped, and only creates cards for the rest.

ShortcutTrello

Create Trello cards from Shortcut stories

A Shortcut + Trello agent flow

Engineering plans in Shortcut; a marketing or launch team tracks the same release on a Trello board and has no reason to learn Shortcut. So the launch board drifts out of date with what's actually being built. This flow mirrors one direction: the agent searches Shortcut with stories-search for stories matching a label or state, and creates a card for each on the Trello list the other team works from using add_card_to_list, carrying the story name, a description that links back to Shortcut, and any labels you map. Shortcut returns stories on request, so the agent reads on a schedule and only stories it hasn't already mirrored become cards.

The flow

Shortcutstories-search

Finds stories with filtering and search.

Trelloadd_card_to_list

Add a new card to a specified list on a specific board.

Step by step

Scope which stories cross over
Pick the Shortcut filter that marks launch-relevant work, such as a 'launch' label or a specific workflow state, and the single Trello board and list cards should land in.
Search Shortcut
The agent calls stories-search with your filter and reads each story's name, state, labels, and URL.
Create the cards
For each story the agent calls add_card_to_list with the name, a description quoting the story and linking its Shortcut URL, and labels mapped onto the board's label set.
Record what's mirrored
Store each Shortcut story ID against the Trello card it created. On the next run the agent skips stories that already have a card, so re-running doesn't clone the board.

Tell your agent

Each morning, search Shortcut for stories labeled 'launch' that are in progress. For any without a Trello card yet, add a card to the 'Launch' list on the Marketing board with the story name, a description that links the Shortcut story, and a matching label. Don't recreate cards for stories already mirrored.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Shortcut install guide Trello install guide

Worth knowing

add_card_to_list places cards on a specific board and list. Resolve the board and list IDs once with list_boards and get_lists, and pass them rather than names.
Trello labels are board-scoped with their own IDs. Map Shortcut labels to existing Trello label IDs ahead of time, or create them with create_label, so the agent isn't guessing.
stories-search can return a large result set on a broad filter. Bound it by state or recent activity so a first run doesn't create hundreds of cards at once.

Questions

Does moving a Shortcut story update the Trello card?: Not in this create-only flow. To mirror state you'd add an update step keyed on the stored story ID that moves the card with move_card when the Shortcut state changes.
How does it avoid duplicate cards?: By storing the Shortcut story ID next to the Trello card ID it created. Each run lists current stories, drops ones already mapped, and only creates cards for the rest.