Who can do this: Administrators and Meeting Managers.
An automation has one trigger and up to 20 steps. When the trigger happens, the steps run in order. This page describes every trigger and step you can choose.
Triggers
Select the Trigger card in the automation, then choose an option under When this happens.
Meeting ended: a live meeting is ended in ClerkDirect. Under Meeting types, keep All meetings checked to match every meeting, or choose specific meeting types.
On a schedule: runs on a recurring date and time. Set Starts on, At (times are on the hour), how often it repeats, and the Time zone.
Document generated: minutes or another document is generated for a meeting. To limit it, list Document kinds separated by commas, for example minutes. A kind must match the whole name; capitalization doesn't matter. You can also filter by meeting type.
Document added: a file is uploaded to a meeting. To limit it, fill in File name contains, for example staff report. Without an asterisk, any file name that contains the text matches. With an asterisk, the whole name must match the pattern, for example *.pdf. Runs start about three minutes after the upload. You can also filter by meeting type.
Document approved: a document review is approved. You can filter by meeting type.
Steps
Select Add step, or the + between two steps, and choose a step in Add a step.
Transcribe recordings: transcribes every recording saved for the meeting, including browser recordings from the live meeting and uploaded audio or video files. Later steps can use the transcripts.
Generate document with Ava: Ava drafts minutes or other documents from your Prompt. Optionally choose a Template (or Let Ava choose) and a File name (leave it empty to let Ava name the file). In a meeting with several sessions, each file adds the session's title, and a name already in use gets a number.
Ask Ava: Ava carries out your Prompt with its workspace tools, such as reading meetings and files, creating tasks, requesting reviews and copying to SharePoint. For example: Create a task for each action item in this meeting's minutes, assigned to the person responsible, due in two weeks.
Create tasks: creates the tasks you define. Each task has a Title, optional Instructions, Assigned to, Due after (days) and Priority. ClerkDirect creates a separate task for each person in Assigned to. A step can hold up to 50 tasks.
Remind about open tasks: adds your Message as a comment on each open task created by this automation, or by another automation you choose under Tasks created by. Up to 200 tasks are reminded per run.
Request review: asks Reviewers to review the document. Choose a Review order (Workspace setting, Everyone at once or In order) and an optional Message to reviewers. It works for uploaded PDF and Word documents and documents Ava generated. The member the run acts as must be an Administrator or Meeting Manager.
Copy to SharePoint: copies the document to the configured SharePoint folder. SharePoint must be connected first; see Connect SharePoint.
What steps need
Transcribe recordings needs a meeting. Use Meeting ended or one of the document triggers; it doesn't work with On a schedule.
Request review and Copy to SharePoint need a document. It can come from a document trigger or from an earlier Generate document with Ava step.
If a step can't find what it needs, ClerkDirect marks it and explains the problem, for example "needs a meeting. Use a meeting trigger such as “Meeting ended”." You can't save until it's fixed.
Placeholders in task text
In Create tasks titles and instructions, and in a reminder Message, you can type these placeholders, each wrapped in double curly braces:
meeting.title, meeting.date and meeting.type: details of the meeting that started the run. In a run without a meeting, they stay as typed.
date: the date of the run.
For example, a task titled Post minutes for followed by meeting.title in double curly braces becomes Post minutes for Regular Council Meeting.