One event system for all your work.

Email, chat, docs, tasks, and calls share one event system. Follow what happened across your whole workspace.

We wanted agents to help when something happens, without someone remembering to start a chat. A customer email arrives, a task gets completed, or a call ends. Those are natural moments to do the next piece of work.

Macro gives email, chat, docs, tasks, and calls one event system. Choose a trigger and instructions for a routine, and an agent can draft a reply, post an update, or turn a call into follow-up tasks. It works with the context already in your workspace and the permissions of the person who set it up.

Act on a customer’s email.

Set up a routine for incoming customer email in Mail. An agent can read the request, create a follow-up task, and draft a reply using the context in your workspace.

Keep the team up to date.

Use a task’s status change to trigger a team update. For example, when an engineering task is completed, have an agent post what changed in the channel where the work was discussed.

Follow up after a client call.

For a real estate team, a finished call can start the follow-up. Have an agent use the transcript to draft a recap and create tasks for the properties the client wants to see.

Setup and reference

Macro has the full company surface: email, team chat, docs, tasks, and calls. The Company graph connects that work. The event system lets agents act when something changes in it.

An email can start a task. A message can start an agent. A finished call can start the follow-up. The trigger and the work it starts live in the same workspace.

Start with an event

Create a routine, give the agent instructions, and choose Add trigger. Triggers include:

A new email arrives.
Someone sends a channel message or @mentions you.
A document is created or deleted.
A task is created, or its status, priority, or properties change.
A call starts or ends.

Limit a trigger to particular items, or use the activity you can access. A routine can have several triggers; any one of them can start it. See the trigger reference for the available settings.

Keep the context and permissions

A routine runs with its creator's permissions. A call-ended trigger includes the participants and transcript, so the agent can work from the conversation.

Agent and bot changes do not fire triggers. Historical email imports do not start new-email routines.

Open the routine's Run History to see what ran and open the agent conversation.