Routine Sharing & Discovery

Share routines with your team using a link, preview them before installing, and reuse proven routine patterns across a team space.

Overview

Routine sharing lets you distribute proven automations across teams without copying configuration by hand.

With sharing enabled, you can:

Publish a share link for a routine
Preview routine details before installing
Install shared routines into another account/workspace
Manage visibility by turning sharing on or off
Promote useful routines into team playbooks people can reuse

Open a routine in Town
Choose Share
Enable sharing and copy the link
Send the link to collaborators

When disabled, the link no longer allows new installs.

Installing a shared routine

Open the shared routine link
Review routine scope and behavior
Click Install
Configure account scope, mode, and any user-specific settings

After install, the routine appears in your routine list and can be customized like any other routine.

Signed-out preview

Shared links support preview even when not signed in, so teammates can review what the routine does before authenticating and installing.

Team Routines

Team Routines are routines intended for a shared team context. They help a team standardize repeatable assistant behavior such as inbox triage patterns, meeting prep, account research, reporting, or task creation.

Use Team Routines when:

More than one teammate should be able to discover or install the same routine
The routine depends on team-level context or integrations
You want to roll out a proven automation without manually recreating it for every person

Town Square is the team surface where shared team activity, team routines, and shared assistant context come together.

What gets shared

Shared routines include the routine configuration needed to run in the destination account. User-specific account connections and permissions remain specific to the installer.

Team-level routines may also depend on team settings or integrations. Review those requirements before installing or enabling the routine.

Always review tools, triggers, and mode before enabling a shared routine in production.

Best practices

Share routines with clear names and short descriptions
Keep instructions concise and outcome-oriented
Validate behavior in a test account before broad rollout
For team routines, document who owns the routine and when it should run
Use approval-required mode first for higher-risk actions

Routines — Stock and custom routine concepts
Custom Routines — Build and iterate your own routines
Safety — Approval and autonomy controls