connect your AI.
drop a spotify link into claude and say “announce this.” it builds your smart link, plans the email touches around your release date, and writes the drafts in your voice, then files the whole campaign into yala, waiting on your approval. release admin, done while you make the next record. the one thing your AI can never do is send: that button stays yours, inside yala.
the gist.
drop a spotify link into claude and say “announce this”: claude previews the release, builds the smart link, plans the email touches around your release date, writes the drafts in your voice, and files the whole campaign into yala as drafts waiting on you. you read them on your messages page, tap approve, done. your audience’s emails never leave yala’s servers; your AI only ever sees counts.
a full run.
friday morning, new single. you say to claude:
here's my new single. set up the release campaign. https://open.spotify.com/track/4uLU6hMCjMI75M1A2tKUQC
- claude checks the workspace: 1,842 reachable people.
- it previews the link, shows you the title + artwork, you confirm, it creates the smart link.
- it proposes the touches around your release date (announce + reminder, plus a last call if you want one) and drafts each email with you, in your voice.
- it files the campaign into yala and hands you the approve link. nothing has sent.
- you open messages, read the drafts, tap approve plan. now they’re scheduled, still yours to edit or pull back.
a couple more prompts that work:
how much of my audience is in germany? worth a segment send?
how did the announce email do? should the reminder change?
connect it once.
every client gets the same connector URL:
https://app.yala.la/api/mcp
- claude: one click: add to claude → (opens claude with the connector pre-filled: review, add, approve). the long way: claude.ai → settings → connectors → add custom connector, paste the URL.
- chatgpt: open the connectors panel → (switch on developer mode), add a connector with the URL.
- grok: grok.com/connectors → new connector → custom, paste the URL.
- cursor: one click: add to cursor →, or settings → MCP → add new server, paste the URL as a remote server.
menu names drift between client versions; if the wording above doesn’t match yours, it’s wherever your client adds a custom / remote MCP server. same URL either way.
whichever client, the last step is the same: your browser opens yala, you pick one workspace, and you approve what the AI may do. connecting is a pro-plan thing; managing and revoking connections lives on your workspace’s connect your AI page.
what your AI can do.
ground itself
before proposing anything it reads the room: list_workspaces and get_workspace for where it’s working, get_coverage and count_subscribers for how many people are actually reachable, messaging_status for which channels exist (email is always on; yala handles the sending), and list_links for what already exists. list_segment_facets and describe_audience_fields show which slices of the audience exist (countries, genres, releases) as counts, never as people.
build the link
preview_release_link turns a pasted streaming URL into a preview (title, artist, artwork) so you confirm it’s the right record before anything is created. then create_release_link makes the smart link, through the exact same gates as the in-app wizard: plan limits, the link-safety screen, all of it.
wait for coverage
a fresh link starts with the three or four platforms the instant preview found; a background scan fills in the rest over the next ~20 seconds. get_link reports coverage as it fills, so your AI waits until the platform list is complete before handing you the link, and rescan_link re-runs the scan for an older link that looks thin.
collect emails on the page
set_link_capture puts an email opt-in form on the link’s landing page (optionally with a first-name field and your own headline and button copy), and get_link_capture reads what’s already set. email and first name only; the form doesn’t collect phone numbers, by design.
route people smartly
conditional redirects send matching visitors straight to a chosen destination: people on iphone to apple music, android to spotify, a country to its local store. suggest_redirects proposes a routing plan built from the link’s own scanned destinations, simulate_redirect tests a visitor (device, os, country) so you see exactly where they’d land before anything changes, and a create / update / remove / list quartet manages the rules. every custom destination passes the same link-safety screen as the link itself.
plan + draft the campaign
plan_release_campaign proposes the touch ladder (announce + reminder by default, with a last-call nudge if you ask for one) anchored to your release date. once the words are right, draft_campaign files it into yala as drafts and hands back an approve link. drafts cannot send. only you tapping approve plan in yala arms them, and after that each touch is a normal scheduled message you can still edit or pull back.
watch it land
get_campaign_status reports what’s approved, what’s scheduled, what sent, and how deliveries went, so your AI can give you the morning-after readout.
good habits.
- one workspace per connection. juggling two artists? approve two grants; each is scoped and revocable on its own.
- read drafts before approving. your AI is a good writer; you’re the one whose name is on the email.
- disconnect clients you stopped using; the connect page lists every grant with a disconnect button.
- if your AI reports a plan gate, that’s yala’s billing telling the truth; the same limits apply in the app.