Muse setup
One-time setup. After this, every save just works.
Settings → Connections → Connect Muse. Sign in first if you need to.
The Client ID works only for your workspace. Keep it with the server value below; Muse asks for both.
In Muse, add a custom connector with these values, then approve the connection when TabTab asks.
Muse opens TabTab’s approval page in your browser. Sign in with the same account that holds the Client ID, then approve. TabTab only receives the findings your assistant chooses to save.
It asks for the whole brief — dek, sections and a hero image — so the first finding arrives looking like the ones on TabTab in Muse.
Research the latest important updates about the topic you picked. Report only genuinely new, source-backed items, and skip anything already saved in the Tab. Consider naming variants — nicknames, tickers, native-language names, venue and promoter terms — even when the exact phrase is absent. Create or update a Tab called "the topic you picked" in TabTab, then push each finding with the full brief shape: title, front-loaded, at most 80 characters preferred and 120 hard, never starting with the Tab's own name; summary, 2-4 plain sentences; dek, 1-3 sentences and at most 400 characters; sections, 2 to 5 of them, each with a title of at most 80 characters, a one-line summary of at most 160, and a body of 2-4 scannable fragments rather than prose; source_url, the page the finding came from; severity, low unless it genuinely warrants attention; finding_type, news or other. Include image when the source has one: a direct landscape hero image URL ending in .jpg, .png or .webp, ideally 1290x970 or larger and under 10 MB, preferring the official source. Omit it rather than guessing — TabTab fills in a stock image when you leave it out. Use at most 10 image URLs per push, and a stable idempotency_key of "<slug>-YYYY-MM-DD" so a retry creates nothing.
Need help? View the detailed setup guide