Work that doesn't end in one service carries on into the next
Work decided in a meeting becomes a task, a leave request moves on to approval, and email to handle comes up in the morning brief. This is because every service uses the same sign-in, the same org chart and the same AI Crew command window. Below, connections available now and the connections coming next are introduced separately.
Designed for: For teams that often copy the same content between several work tools.
Connections available now
The scenes below use Ondam Living Co., a fictional online home goods brand, as an example.
Email to handle, today's events, approvals waiting and tasks come together in the assistant AI Crew's morning report. The launch manager starts with today's work instead of opening each service one by one.
"Confirm the product page photo shoot date", decided in the mug set launch meeting, goes straight from the meeting record into a task, and an owner is assigned.
During the launch meeting, the meeting content builds up in the Notes tab, and when the meeting ends, the summary, attendees and tasks are recorded. Type /회의 (Korean for "meeting") in a planning note to insert that meeting record as a card.
When opening the launch meeting, bring in the mug set product specification from Drive as meeting material.
When the logistics manager requests leave, it moves on to Approval and is approved along the approval line from the org chart. The result also arrives as a phone notification.
When a work request, such as providing a laptop to a new support agent, needs approval, it continues into Approval.
Share tasks, notes, meetings, approvals and contacts as cards in the Messenger launch channel. Tap a card to go to the original screen.
Attach an OEM quote from Drive or a plan from Notes to the AI Crew command window and hand off a summary or a draft.
The results of web work done with Crew Browser are left as result cards in the AI Crew command window and Messenger.
Connections coming next
The connections below are in preparation or in beta. Beta items are being turned on service by service.
| Connection | What it does | Status |
|---|---|---|
| Drive → Mail | Attach Drive files to email directly | In preparation |
| Mail → Messenger | Share email in Messenger as a card | In preparation |
| Notes → Mail | Put a note into the email body | In preparation |
| Drive → Calendar | Copy Drive files to an event | In preparation |
| Calendar → Messenger | Share an event in Messenger as read-only | In preparation |
| Voice recording → Notes | Make meeting minutes from a recording | In preparation |
| Search → AI Crew | Ask AI Crew based on search results | In preparation |
| Tasks → Calendar, Today and mobile | Show tasks on the calendar, and in Today and the mobile list | Beta |
| Contact Center → CRM | Connect support conversations with a customer relationship management system (CRM) | In preparation |
| Accounting → tax agent | Share the same ledger with your tax agent | In preparation |
Related services
Gathers scattered work into a morning report.
Meeting records carry on into Notes and Tasks.
Assign and track work that comes from meetings and Messenger.
Leave and work requests continue into approval.
Share cards from several services in conversation.
Frequently asked questions
Who takes on the tasks decided in a meeting?
You choose the owner when you turn something from the meeting record into a task. The person who receives it can accept, decline or pass it on to someone else, and gets progress updates as notifications.
Do we need to set up connections between services separately?
Services inside crewai.work use the same sign-in and org chart, so you don't need to connect them to each other separately. Each person uses only the services their role allows.
What happens if the person who receives a shared card doesn't have permission to see the original document?
Even when they tap the card and go to the original screen, they see only what their own permissions allow.
Related pages
Start with AI Crew in the November closed beta.