What is Studio?
Studio is where your automations live. An automation is a small set of steps that Harmony carries out for you, without anyone clicking anything.
For example:
- When a meeting summary is ready, write a short follow-up email and send it to the contact.
- One hour before a customer call, send the owner a short prep note.
- Every day at 09:00, summarise the previous day's meetings.
You do not build automations by hand. You describe what you want to the Companion, and it creates the automation for you. Studio is where you then see it, switch it on or off, and check what it did.
Where to find it
Open Studio from the sidebar, under Enterprise Meetings.
If a run needs your attention, a warning icon appears next to Studio in the sidebar. Selecting it takes you straight to the run that stopped.
Turn it on
Studio is off until three things are true. If any one of them is missing, you see "Studio isn't available here" instead of the list.
-
Harmony has rolled Studio out to your workspace. This one is on our side. If the switch described below is not on your Experimental page, your workspace is still waiting.
-
A workspace admin has turned it on. Open Settings → Experimental, turn on Studio Automations, and select Save changes. Changing this requires an admin.
-
Your role includes access to automations. See Who can use it below.
While Studio Automations is off, no automation runs for the workspace. Saved automations are kept, but events that happen while it is off are not queued up and replayed later.
Who can use it
What matters is that your role includes automations permissions. Reading the list needs automations:read; activating, deactivating, and re-running need automations:update; deleting needs automations:delete.
This does not have to be a new role. A workspace admin can add automations permissions to any existing role, or create a new one — whichever fits how your workspace is organised. See Roles and permissions.
Of the three built-in roles, only Admin includes automations permissions by default. Team Manager and User include none, so they cannot open Studio until someone adds them.
Check their role before anything else. A workspace can have Studio switched on and still have most of its members unable to see it, because their role carries no automations permissions.
Automations are also private to the person who owns them. You see the automations you created, not your colleagues'.
What's in an automation
Every automation is one trigger followed by one or more steps.
- The trigger decides when it starts — something happening, a repeating schedule, or a time relative to something in your calendar.
- The steps are what it does — ask an agent to do a task, check a condition, or use one of your connected tools.
You can see this laid out as a diagram on the automation's Editor tab. The diagram is there to read, not to edit.
What's next
- Create an automation — ask the Companion, and choose what starts it.
- Check what an automation did — read its runs, and restart the ones that stopped.