On mention
File bugs from support
Reproduces the report and opens a clean Jira issue.
Recurring issues agentFix the cause, not the ticket.
Every Friday it reads the week's tickets, groups them by root cause, and counts each group. You get a small table and a note on which problem to fix first.
Your first signup includes $50 in free credits.
Fridays · 15:00
Find the problems that keep coming back
- Reads
- A week of tickets
- Grows
- Groups and counts
- Lands in
- Sheets and Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every Friday at 3, read this week's tickets in Zendesk. Group them by cause, count each group, add the rows to my Issues sheet, and post the top three in Slack.
TulipFarm
I made an agent called Issue finder and a Friday 15:00 schedule. It reads tickets through your Zendesk Custom MCP connection. Adding rows to Sheets and posting to Slack asks you first. Activate it?
ActivateEdit first
One week, grouped.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Fridays at 15:00
Run startedStarted - Reads
This week's tickets in Zendesk
120 tickets - Writes
Groups by cause, with a count and an example each
6 groups - Checks
Groups bigger than last week
2 growing - Asks first
Add rows to Sheets and post the top three to Slack
Approved - Saves
Rows in Google Sheets, note in Slack
DeliveredCompleted
What lands in your sheet.
One row per cause. The change column shows what is getting worse.
Issues · this week| Cause | Tickets | Change | Example |
|---|---|---|---|
| Sign-in loop on mobile | 31 | Up | Ticket #2201 |
| Export fails on large files | 22 | Up | Ticket #2187 |
| Invite email delayed | 18 | Same | Ticket #2175 |
| Billing date confusion | 12 | Down | Ticket #2190 |
What gets planted.
Three parts you own and can change at any time.
- Agent
Issue finder
Groups tickets by cause and counts them.
- Table
Issues
One row per cause, week after week.
- Workflow
Fridays 15:00
Runs once a week.
Uses
- ZendeskMCPZendesk
- Google Sheets
- Slack
Add if you use it
- Jira
Confluence
MCPFreshdesk
It reads quietly. It asks before it acts.
Reads without asking
- Tickets from the last 7 days
- Last week's rows in your sheet
Asks you first
- Adding rows to Google Sheets
- Posting to Slack
- Opening any Jira issue
It uses your own connections, so it never sees more than you can.
Grow it your way.
Send the top cause to engineering
Offer to draft a Jira issue for the biggest group.
Trend over a month
Compare with the last four weeks, not just the last one.
Split by plan
Count groups separately for each customer plan.
Questions, answered.
How does it decide the groups?
The agent reads each ticket and names a cause using the labels in your instructions. You can edit the labels any time.
Are the counts exact?
They come from the tickets it read. Each row has an example ticket so you can check it.
How does it reach my help desk?
Through a Custom MCP connection. Add the server, pick the sign-in method, and review each tool first.
Weekly
Turn fixes into help articles
Solved tickets become draft articles in your knowledge base.
ZendeskMCP
Mondays · 8:00
Collect what customers are saying
Pulls feedback from tickets and forms into themes and quotes.
Know what to fix on Monday.
Public beta, open to everyone. Your first signup includes $50 in free credits.