Collaborate with your agents where your team works.

Once your Notion workspace is connected, mention the agent in a comment. It reads the page, does the work and replies underneath. Answer in the thread to keep going.

Fernhill / Operations / Lisbon trade fair Edited just now

Lisbon trade fair

Owner
Jonas Brandt
Status
Planning
Dates
November 12–14

Meeting notes · 9 October

  • Booth confirmed: hall 2, stand B12
  • Marta Silva asked for a joint demo slot on day two
  • Brochures need the new prices before they go to print

Action items

  • Book booth staff for all three days Jonas
  • Reprint brochures with new prices Lena
  • Book the hotel for three people Jonas
  • Reply to Marta about the demo slot Mira
Action items
Jonas Brandt 09:12
@Wanda can you turn these into tasks on the trade fair checklist and assign them?
Wanda Operations agent 09:13
Added four tasks to the trade fair checklist. Booth staff and the hotel are yours, the brochure reprint is Lena’s. Nobody took the reply to Marta in the meeting, so I left it open.
No new mention needed
Jonas Brandt 09:20
Give that one to Mira, due Friday.
Wanda Operations agent 09:20
Done. Mira has it, due Friday.
Reply…
  1. 01

    Link the agent to a Notion user

    Install the zwrm connection in your workspace once and choose the pages it may see. Then link each agent to a Notion account of its own.

  2. 02

    Mention it on a page

    Write @ and the agent’s name in a comment or in the page text. It reads the page, does the work and answers right there.

  3. 03

    Reply to keep going

    Each discussion keeps its own session. Answer in the thread and the agent continues where it left off.

Forward emails to your agent.

In Outlook, forward an email to the agent’s own Microsoft 365 account. In Front, give it a shared inbox to work through. Either way, a reply can wait as a draft until a person has checked it.

Outlook

Forward an email to the agent’s address. It answers you in the same thread and drafts the reply to your customer.

Fw: Invoice 2017: wrong VAT ID 2 messages
Mira Novak To: Hedi 09:38

Hedi, can you take care of this?

Kestrel GmbH, accounts Invoice 2017 still shows our old VAT ID. Please send a corrected copy.
Hedi Finance agent To: Mira Novak 09:41

I corrected invoice 2017 and drafted the reply. Shall I send it?

DraftTo: Kestrel GmbH, accounts

Dear Kestrel team, please find the corrected invoice 2017 attached. Kind regards Fernhill finance

PDFInvoice-2017-corrected.pdf

Front

Share an inbox with the agent. It reads new conversations, tags them and drafts replies.

E Erik Lund, Aster AB To: support@fernhill.eu 08:02

Hello, two items from order #2049 arrived damaged. Can you send replacements? Best regards Erik Lund

Draft by Carla To: Erik Lund

Dear Mr Lund, sorry about that. We will send replacements tomorrow, and you don’t need to return the damaged items. Kind regards Fernhill customer service

Message your agent in Teams.

Give the agent its own Microsoft 365 account and chat with it like a colleague, one to one or in a group chat. Each chat is one ongoing conversation, so a follow-up can build on the last answer.

Teams

Chat

  • ElsaAdded an August sheet and posted…
  • Lena WeberSee you at 2
  • Jonas BrandtBooth staff is booked

Teams and channels

  • # Fernhill › General
  • # Fernhill › Sales
Elsa Reports agent Available
ChatFiles
10:24 Can you put September’s orders by customer into a spreadsheet?
Elsa Reports agent 10:26
Here it is: 412 orders from 38 customers. Northwind and Kestrel ordered the most.
Orders by customer.xlsx
Excel workbook · 36 KB
10:31 Now the same for August, in the same file. And post the comparison in Sales.
Elsa Reports agent 10:32
Added an August sheet and posted the comparison in Sales. Kestrel went from 61 orders to 44, the others moved by less than 5%.
F# SalesFernhill
Elsa Reports agent 10:32
Orders by customer · September vs. August
412 orders in September, 9 more than in August. Kestrel placed 44 orders, down from 61. Both months are in the workbook.
Orders by customer.xlsx
Excel workbook · 36 KB
  • Answers one-to-one and group chats from its own account
  • Keeps one conversation per chat, files included
  • Posts and replies in channels when you ask it to
  • Can show as available in Teams while it’s switched on

Assign your agent an issue.

Assign an issue to the agent’s own GitHub user or mention it in a comment. It makes the change on a branch, opens a pull request and reports back in the issue.

fernhill/website Code Issues 12 Pull requests 3

Add the Lisbon trade fair to the events page #87

Open opened by lena-weber

lena-weber commented 10:58

The fair is on 12–14 November, hall 2, stand B12. Please add it to the events page before Thursday’s newsletter.

lena-weber assigned fernhill-pia 10:58
fernhill-pia commented 11:04 Writing agent

Opened #88. It adds the fair to the events page with the dates, the hall and the stand number.

Add Lisbon trade fair to the events page #88 fernhill-pia wants to merge into main from lisbon-trade-fair Open
lena-weber commented 11:19

@fernhill-pia please add the German page as well.

fernhill-pia commented 11:23 Writing agent

Added the German page to #88. Both are ready for your review.

  1. 01

    Assign or mention it

    Assign the issue to the agent’s GitHub user, request its review or mention it in a comment.

  2. 02

    It opens a pull request

    The agent clones the repository, makes and checks the change on its own branch, opens a pull request and comments on the issue.

  3. 03

    You review and merge

    It never pushes to your default branch and never merges unless someone asks it to. Ask for changes in a comment and it updates the pull request.

Each agent signs in as itself. With only the access its account has.

An agent never borrows a colleague’s login. It gets its own account in each tool, so you can see what it wrote, limit what it reaches and take access back.

dashboard.zwrm.eu / Integrations / Notion

Replies as itself

Comments, emails, chat messages and pull requests come from the agent’s account, so everyone can see who wrote what.

Only its own access

The agent sees and edits what its account is allowed to, nothing more. Its credentials stay in zwrm and never enter the machine it runs on.

Access you can revoke

Unlink an agent or disconnect a tool in the dashboard at any time, or remove the account in the tool itself. An agent without its own sign-in is refused.

Every run logged

Each run is logged in the dashboard with what started it, every tool call and the result. Tools you mark for approval pause the run until someone says yes.

Connect a tool once. Then choose which agents work in it.

An admin connects each tool for the whole workspace. Every agent then signs in with its own account, and only the agents you link can work there.

  • Notion

    Agents answer mentions in comments and page text, and read the pages and databases shared with them.

    How it works in Notion
  • Microsoft 365

    Outlook, Teams, calendar and files, from the agent’s own work account. Agents read and draft emails, answer chats and work with Excel and SharePoint files.

    How it works in Microsoft 365
  • Front

    Agents read conversations in the inboxes you share, draft replies, leave comments for your team and add tags.

    How it works in Front
  • GitHub

    Agents take assigned issues and mentions, push a branch, open a pull request and report back in the thread.

    How it works in GitHub
  • HubSpot

    Agents log calls and emails to the right deal and draft follow-ups for deals that have gone quiet.

    How it works in HubSpot
  • DATEV

    Agents match incoming invoices to orders, file them for DATEV and draft payment reminders.

    How it works in DATEV

Tell us what lands on your desk every week. We’ll show you an agent doing it.

A demo with our team, in English or German. Bring one recurring task and the tools it touches.