Best for
- Brand and community managers who need spikes in sentiment before they become a support or public-relations issue.
- Social and support leads who need only the mentions that require a reply, not every mention.
Connectors
Before you start
Have the brand name or handles you care about, a Slack channel for alerts, and a Notion database for the archive. Agent will ask for your X Bearer Token. Create an account at console.x.com and generate a Bearer Token there. Add credits on your X developer account. Without credits, mention search on X will fail.Prompt the agent
What to expect
Agent watches for mentions, scores which ones matter, posts a short summary to Slack, and saves the thread in Notion. Review the first batch and tighten what counts as “important.” If mentions never come in, check that the Bearer Token is set and the X developer account has credits. After the first morning run, open a Slack alert, click through to X, and confirm the Notion row has the same link.Make it work for you
Troubleshooting
- Mentions never come in: confirm the X Bearer Token is set and the X developer account has credits. Without credits, mention search fails even with a valid token.
- Slack is silent but Notion fills up: Agent may be treating everything as noise. Tighten what counts as “important,” or ask it to post a daily digest even when nothing needs a reply.
- The archive is messy: point Agent at a Notion database with columns you already use (date, link, sentiment, needs reply). Ask it to map to those fields instead of creating a new page each time.
Related
Analyze customer feedback
Same Slack and Notion setup for support tickets.
Monitor competitors
Same Slack alerts and Notion archive for competitor sites.