/ For everyone at Yuno

Imagine having an assistant
that actually uses your tools.

We built a platform where you can create AI assistants that connect to the tools you already use every day — Gmail, Slack, Calendar, Jira, Drive, GitHub, and Confluence. They can read your emails, check calendars, create tickets, search documents, and post on Slack. For real. This page is here to help you think about how that could help you.

Show me examples
Gmail
Read, search, draft, send emails
Calendar
Check availability, create meetings
Drive
Find docs, create documents
Slack
Read and send messages, threads
Jira & Confluence
Tickets, pages, search
GitHub
Repos, PRs, issues, code
/ How to think about it

Think of it as a coworker that never sleeps.

A Yuno Agent is like a team member that you can give a specific job to. You tell it what to do, you give it access to the tools it needs, and it does the work. It can:

Read & Search

Search your Gmail inbox, read Slack threads, find documents in Drive, look up tickets in Jira, search Confluence pages. It can pull information from all these places at once.

Write & Create

Draft emails, create Google Docs, post messages on Slack, create Jira tickets, write Confluence pages, schedule meetings on Calendar. You can review everything before it sends.

Work on a Schedule

Run every morning at 9am. Run every Friday at 4pm. Run 30 minutes before each meeting. You set the schedule, it does the work automatically.

Work as a Team

Multiple agents can work together in a chain. One agent screens candidates, the next one schedules interviews, the next one writes the debrief. Each one passes its work to the next.

The key question to ask yourself: What do I do every week that's repetitive, involves copying information between tools, and doesn't require deep thinking — just time?

/ Real examples

What could this look like for you.

Click on any example to see the before/after and how it would work step by step.

"I open my inbox Monday morning and there are 80 unread emails"
Half are notifications you can ignore. 10 need a reply. 3 are urgent. 1 has a deadline you missed on Friday. You spend the first hour of your day just figuring out what matters. By the time you're done, you've lost your most productive morning hours.
Today
  • Open inbox, scroll through 80 emails
  • Try to figure out which ones are urgent
  • Open each one, read, decide if you need to reply
  • Forget to reply to 3 of them
  • Miss a deadline buried in email #47
  • Spend 45 minutes total just triaging
With an Agent
  • Agent scans your inbox every morning at 8am
  • Sends you a Slack DM: "3 urgent, 10 need reply, rest are FYI"
  • Drafts replies for the routine ones (you review before sending)
  • Creates Calendar reminders for emails with deadlines
  • Flags anything from leadership or clients as high priority
  • You start your day knowing exactly what needs attention
"I walk into meetings without context and spend the first 10 minutes catching up"
You have 6 meetings today. You can't remember what was discussed last time, who the client is, or what the open action items are. You spend the first 10 minutes of each meeting asking "where were we?"
1
30 minutes before your meeting, ask the agent to prep you — or set it to do it automatically for every meeting on your Calendar
2
The agent finds related documents in Drive — last meeting notes, shared decks, proposals
3
Checks Jira for any open tickets related to the meeting topic or the attendees
4
DMs you on Slack with a 1-minute briefing: what was discussed last time, what's pending, what docs to review

You walk into every meeting prepared. No more "let me pull up the notes..." — you already have them.

"I compile a weekly report from 4 different sources and it takes half a day"
Every Monday you pull data from Jira (tickets closed), email (merchant requests), Confluence (process updates), and Slack (escalations). You copy-paste it all into a Google Doc, format it, and share it with leadership. Same thing every week.
1
Every Monday at 8am, the agent starts gathering data automatically
2
Searches Jira for tickets resolved last week, groups by category
3
Scans Gmail for merchant requests and escalations from the past week
4
Checks Confluence for any process updates or policy changes
5
Creates a Google Doc with the full report, formatted and ready to share
6
Posts the summary in Slack and shares the doc link with the leadership channel

Your Monday report writes itself. You review it, add any personal commentary, and share. Half a day becomes 15 minutes.

"I spend 3 days just screening CVs every time we open a role"
You open a Senior Engineer role. 200 CVs arrive via email over 2 weeks. You read each one, compare it against the job description, rank candidates, coordinate 4 panel interviews across timezones, collect feedback from Slack threads and emails, write a debrief, and prep the offer letter. Total: ~8 working days.
Today
  • Read 200 CVs one by one from your inbox
  • Open the job description doc, compare manually
  • Build a shortlist spreadsheet by hand
  • Email each interviewer to find availability
  • Go back and forth 5 times to find a time that works
  • Chase feedback from 5 interviewers across Slack and email
  • Copy-paste feedback into a debrief doc
  • Fill in the offer letter template
With an Agent Team
  • Agent reads all CVs from your inbox automatically
  • Compares each one to the job description in Drive
  • Gives you a ranked shortlist with scores and notes
  • Checks everyone's Calendar and proposes interview times
  • You pick one, it sends the calendar invite and confirmation email
  • After interviews, it reads all feedback from Slack and email
  • Creates a single debrief document with everything consolidated
  • Drafts the offer letter — you review and send

Your time goes from ~8 days to a few hours — you're reviewing a shortlist, picking interview times, and approving an offer letter. The agent does the searching, comparing, scheduling, and writing.

"Every Friday I waste 2 hours writing sprint reports that nobody reads"
End of sprint. You open Jira, count tickets, cross-reference with GitHub PRs, figure out velocity, identify blockers, write it all up in a doc, and post a summary in Slack. Meanwhile, the Confluence docs are 3 sprints behind and bug reports from Slack still haven't been turned into Jira tickets.
Today
  • Open Jira, manually count completed vs planned tickets
  • Cross-reference with GitHub PRs to see what actually shipped
  • Calculate velocity by hand in a spreadsheet
  • Write the sprint summary in a Google Doc
  • Post it in Slack, tag stakeholders
  • Go back to Slack to find bug reports and create Jira tickets
  • Notice Confluence docs are outdated, add it to your TODO list
With an Agent Team
  • Every Friday at 4pm, agent pulls data from Jira and GitHub
  • Counts tickets, PRs, calculates velocity automatically
  • Writes a formatted report and saves it in Drive
  • Posts the summary in your team's Slack channel
  • Another agent watches Slack for bug reports all week
  • Creates structured Jira tickets within minutes of a report
  • Another agent detects outdated Confluence pages and updates them

You get your Fridays back. Bug reports become tickets in minutes instead of days. Docs stay current. You focus on your team, not on admin.

"Every new hire means 6 meetings and 4 emails — all created manually"
A new engineer starts Monday. You need to schedule their Day-1 welcome, week-1 check-in, team introductions, and 30-day review. Send them links to the handbook, policies, and team Slack channels. Every. Single. Time.
Today
  • Schedule 6 meetings on Calendar, check everyone's availability
  • Send welcome email with links to handbook, policies, channels
  • Post announcement in #general
  • Send follow-up emails with training materials
  • Follow up in 2 weeks to make sure everything was done
  • Total: ~2 hours per new hire
With an Agent
  • You tell the agent: "New hire, John Smith, Senior Engineer, starts Monday"
  • Checks everyone's calendars and schedules all 6 meetings
  • Drafts the welcome email with all the right links from Drive
  • Posts the announcement in #general on Slack
  • Sends training materials links from Confluence
  • Total: you review and approve in ~10 minutes
/ Thinking bigger

Multiple agents working together.

The examples above are single agents. But you can also chain them together — one agent's output becomes the next agent's input. Here are three full pipelines we've designed and could build:

Hiring Pipeline — 5 agents

Screen CVs
Evaluate culture fit
Schedule interviews
Summarize feedback
Draft offer letter

First agent screens 200 CVs and creates a shortlist. Second agent evaluates culture fit using your interview guides from Confluence. Third agent checks Calendar availability and schedules all interviews. Fourth agent reads all feedback from Slack and email and consolidates a debrief. Fifth agent drafts the offer letter.

Engineering Ops Pipeline — 5 agents

Review PRs
Triage bugs
Write release notes
Sprint report
Update docs

First agent reviews every new PR on GitHub for security and quality. Second agent watches Slack for bug reports and creates Jira tickets automatically. Third agent generates release notes from merged PRs and resolved tickets. Fourth agent compiles sprint metrics every two weeks. Fifth agent detects outdated Confluence pages and updates them.

Internal Q&A Pipeline — 5 agents

Detect question
Search all sources
Generate answer
Flag knowledge gaps
Weekly digest

First agent detects questions in Slack. Second agent searches Confluence, Drive, and past conversations. Third agent writes a clear answer with source links. Fourth agent flags questions that couldn't be answered and creates doc requests. Fifth agent compiles a weekly digest of top questions and knowledge gaps.

/ Transparency

Where we are right now.

This is an honest look at what's ready and what's not.

Ready

  • ✓ The platform to deploy and manage agents
  • ✓ Dashboard to chat with agents and monitor them
  • ✓ Connections to Gmail, Calendar, Drive, Slack, Jira, Confluence
  • ✓ Pipeline engine to chain agents together
  • ✓ Agents can live in Slack and respond to messages
  • ✓ Scheduled tasks (run every morning, every Friday, etc.)

In progress

  • ◯ Pre-built agent templates for specific roles
  • ◯ Pre-built pipeline templates (hiring, engineering, Q&A)
  • ◯ Approval workflows (review before the agent sends/creates)
  • ◯ More tool connections (Salesforce, Datadog, Deel, etc.)
  • ◯ Personal productivity agents (email assistant, meeting prep)
Access the platform
Open https://agents.internal-prod.y.uno — you need to be connected to the Development VPN for it to work. Log in with your @y.uno Google account.
/ Questions

You might be wondering.

Can it access my emails and calendar without me knowing? +
No. You have to explicitly connect your Google account, and you choose exactly what the agent can access. You can disconnect at any time. Think of it like granting an app permission on your phone — you're always in control.
Will it send emails or create tickets on its own? +
Not unless you explicitly tell it to or schedule it to do so. By default, agents only do what you ask them to do in that moment. If you want it to run automatically (like every Friday), you set that up yourself. Nothing happens without you initiating it.
Do I need to be technical to use this? +
No. You configure an agent by telling it what you want it to do in plain language — like "every Monday, check my Gmail for unread emails from clients and summarize them in a Slack DM". No code required. The team can help you set up your first agent.
I have an idea for something I want to automate. What do I do? +
Message us at @ai-crew in Slack. Tell us: what do you do today, how often, and what tools are involved. We'll help you figure out if an agent can do it and how to set it up. The more specific you are, the faster we can help.
Can I try it right now? +
Yes — go to https://agents.internal-prod.y.uno (you need the Development VPN). The platform is running and the tool connections work. We're building the pre-configured templates right now. If you want help setting up a custom agent for your use case, reach out to @ai-crew on Slack.

What would you automate?

Think about the most repetitive part of your week. Then come talk to us.

@ai-crew on Slack