Turn scattered project updates into a useful brief.
Before a website launch call, an agent checks the team’s calendar, emails and tasks. It prepares a brief, spots missing details and asks before creating follow-up work.
Follow the workflow
Watch the overview, then explore each step below.
Read the video transcript
Tomorrow's website launch call is booked. Are you ready? The agent checks the calendar, client emails, and Asana tasks. Spot the missing approval and access details before the call. Build a meeting brief from the client's emails and project history. Review the suggested follow-ups and choose what the agent should do. Once approved, the agent creates the tasks and links the brief. See this for your business. Request a personalized demo.
- 01
Ask for preparationSlack → n8n - 02
Read the right sourcesGoogle Calendar · Gmail · Asana - 03
Spot the loose endsGmail → n8n - 04Prepare the briefGoogle Docs
- 05Ask before actingSlack
- 06Create approved tasksn8n → Asana
Ask for preparation
Lorna Price at Latchkey Web Co. asks for a brief before Marlow Electrical’s website launch call. The request allows reading and drafting; creating tasks needs approval.
- Project
- Marlow Electrical website
- Meeting
- 27 Oct · 10:00
- Requested by
- Lorna Price
Read the right sources
The agent gathers the meeting, the client email thread and the matching Asana project. It keeps them tied to the same client without changing tasks or contacting the customer.
- Client
- C-1077 · Marlow Electrical
- Contact
- Gareth Hinds
- Changes to source records
- None
Spot the loose ends
The promised homepage approval has not arrived, and domain access is still missing. The agent identifies both from the client’s messages and keeps the contact-form test open.
- Homepage approval
- Still missing after the promised time
- Domain access
- Not received
- Contact-form test
- Still open
Prepare the brief
BRIEF-024 brings the evidence and project context together, with links back to the original notes. Two follow-up tasks are proposed, ready for Lorna to review.
- Brief
- BRIEF-024
- Evidence
- NOTE-44, NOTE-45 and the form test
- Asana tasks created
- 0
Ask before acting
Lorna reviews the proposed task titles, owners and deadlines. The workflow waits for her approval before creating anything in Asana.
- Reviewer
- Lorna Price
- Proposed deadline
- 27 Oct · 09:00
- Client emails sent
- 0
Create approved tasks
After approval, the agent creates TASK-201 and TASK-202 with the agreed owners, deadlines and brief link. The tasks remain open for the people doing the work.
- Tasks
- TASK-201 and TASK-202
- Context
- BRIEF-024 linked
- Status
- Open · assigned to the agreed owners
Fictional sample data. These simplified views show how your existing tools could work together. This walkthrough doesn’t run AI, send messages, or connect to live systems.
A prepared brief and clear follow-ups inside the tools your team uses.
This is a workflow concept, not a promise of measured results. Equivalent implementations depend on the systems and process involved.
What we would work through together
- Choose which sources the agent may read and how it identifies the right client or project.
- Keep the original evidence linked so the team can check the brief’s conclusions.
- Separate permission to read and draft from permission to create tasks or send messages.
- Agree who approves actions, how failures are surfaced and what happens when evidence is missing.
What keeps needing
another follow-up?
Show us where enquiries, quotes or client handoffs get stuck.
We’ll help you see the scope, the cost and a better way through.