Documentation Index
Fetch the complete documentation index at: https://docs.gc.ai/llms.txt
Use this file to discover all available pages before exploring further.
Automations are recurring GC AI chats. You set the task up once with the instructions, skills, files, playbooks, and context it needs, then pick a schedule. Each run starts a fresh chat with the results, so you have a stable record of every weekly scan, monthly review, or scheduled briefing.
Each Automation run produces a new chat in your history, the same way any other GC AI conversation does. The chat is named for the automation and dated for the run, so you can compare results across weeks. Open it, edit it, share it, branch from it, or carry the conversation on manually like any other chat.
What You Can Do with Automations
- Connect an automation to a project so every run uses the project’s files, instructions, and prior chats as context.
- Share with teammates at read, write, or admin access — or make an automation visible to your whole organization.
- Pause and resume when the work is on hold (a regulatory pause, a deal that is sleeping, a holiday week).
- Run manually at any time without changing the schedule.
- Duplicate an automation, or Copy and Customize one shared with you, to use as the starting point for a new variant.
- Get an email when each run finishes so you can read the results when you have a minute.
Where to Find Automations
Automations show up in several places in GC AI:Automations page
Open Automations from the left sidebar. This is where you can view and create all your automations.
Create menu
- Click the + button.
- Select New automation.
Projects page
Create or attach an automation to a project so each run inherits the project’s files, instructions, and chat history.
Skills
From any skill, click the Zap icon (or Automate this skill) to start a new automation pre-attached to that skill.
Setting Up an Automation
The setup is short. Open the automation form from any of the entry points above, then:- Create the automation and give it a clear, specific name (for example, “Weekly Ohio construction-law update”).
- Add a description so teammates know at a glance what the run does.
- Write the instructions GC AI should follow each time. Treat it like a short brief: the instructions need to stand on their own, since there is no live back-and-forth during the run.
- Attach the resources the run depends on:
- Skills (for example, a regulatory-scan skill or a playbook-review skill)
- Files and folders (uploaded materials, your standard templates, internal memos)
- Playbooks (when the run is reviewing a playbook itself or applying one)
- Company profile, labels, or a project for organization-aware context
- Pick a schedule. Choose Daily, Weekdays, Weekends, Weekly (one day a week), or Custom (any combination of days), then pick the time and time zone.
- Turn on email notifications if you want a note in your inbox when each run is ready.
- Save. The automation runs on the schedule you picked, and you can also run it manually any time from the automation page.
Example Workflows
A few patterns we see in-house teams set up first:Weekly regulatory scan for a jurisdiction
A weekly scan of new and proposed legislation, regulatory guidance, and enforcement actions in a single jurisdiction (for example, Ohio construction law). Attach a research skill, set the scope in the instructions, and let GC AI deliver a Monday-morning briefing each week.Scheduled playbook review
A monthly check that keeps a playbook current with changing law. Attach the playbook itself and a “review for legislative drift” skill. GC AI reads the playbook, scans for regulatory developments since the last run, and flags clauses that may need updating.Weekly legal ops briefing
A weekly digest of what is happening across a matter or workstream. Connect the automation to a project, attach the relevant memos and uploaded materials, and write instructions that ask for a structured briefing (priorities, blockers, decisions needed). Each Monday you get a fresh chat with a teammate-shareable summary.Daily briefing across calendar, email, and Slack (coming soon)
A daily synthesis that pulls from your calendar, email, and Slack alongside the resources you attach. This is on the roadmap and will arrive once GC AI’s connectors ship. It is not part of this launch.Sharing and Ownership
Each automation has a single creator. The creator owns the schedule, the run history, and any destructive actions (delete, share, change visibility). To bring teammates in, you have two options:- Share with specific people. Open the automation menu and pick Share to grant Read, Write, or Admin access to individual teammates. Everyone you share with sees the same automation; edits made by anyone with Write or Admin access apply to that one shared automation.
- Make it visible to your whole organization. From the share dialog, turn off access controls to publish the automation to the Organization tab so anyone in your org can find it.
- Run history stays with the creator. Only the creator sees the list of past runs and the chats they produced. Teammates with access can read and edit the configuration and run it manually, but the run log on the page is creator-only.
- Attached skills are shared along with the automation. If your automation references private skills you’ve authored, GC AI grants the people you share with read access to those skills automatically. Be thoughtful about what you attach before sharing.
- Project-attached automations follow the project’s access — anyone who can see the project sees the automation in its Automations section.
Notifications
You can turn on email notifications inside any automation. When each run finishes, GC AI emails you with a link to the new chat. Slack notifications are on the roadmap.Best Practices
A few patterns from the in-house teams using Automations well:- Write self-contained instructions. A run cannot ask a clarifying question. Spell out the audience, the format you want, the depth you want, and what to do when sources disagree.
- Attach stable resources. Pick the skills, files, and playbooks the run needs and keep them stable. If you rename a file or rework a skill mid-quarter, your run picks up the new version on the next schedule, which is usually what you want, but worth knowing.
- Connect to a project when context matters. If the run is about a specific matter or workstream, link it to the project so the run sees the prior chats and shared files automatically.
- Be thoughtful about sharing. Sharing grants access to the same automation (not a copy), and any private skills attached to it become readable to the people you share with. Audit the attached resources before you share.
- Pause when the work is on hold. A paused automation skips its schedule and is one click away from resuming, with the configuration intact.
- Treat the first run as a draft. Read the first chat carefully, refine the instructions, then let the schedule do its job.