Templates are pre-built workflows you can install with one click. Browse the public catalog at /templates or share your own.
#Browse and install
Open the template catalog from the sidebar or the workflow builder. Each template shows:
- Name and description
- Required integrations (Gmail, Stripe, Slack, etc.)
- Install count
- Category tags (SaaS ops, content, client management, e-commerce, etc.)
Click Install to copy the template into your workspace as a new workflow. Installed templates are full copies: they’re yours to edit, and they don’t receive updates from the original.
If a template needs integrations you haven’t connected, Rills lists the missing ones after install. Connect them, then run the workflow.
#During onboarding
The welcome screen surfaces a curated set of templates so new users can start from a working example. Same templates as the public catalog, just shown at the right moment.
#Sharing your own
Publish any workflow as a template:
- Open the workflow (it must have a published version to share).
- Click Share → Publish as template.
- Add a name and description, optionally set an expiry (up to 365 days).
You get a unique URL. Anyone with the URL can install it. The shared definition is sanitized: credentials, secrets, and workspace-specific data are stripped. If the workflow uses workspace agents, their definitions travel as snapshots so the installed workflow has the same agent contracts. Platform agents are reused as platform defaults.
#Updating a shared template
A shared template is a snapshot of the workflow’s published version, captured the moment you shared it. Edit the source workflow and share again to publish an updated snapshot; it gets its own new URL, and the original URL keeps the version it captured. Installs copy the snapshot from whichever URL they use.
#Customization
Once installed, a template is a regular workflow. Change triggers, swap integrations, add or remove nodes: the installed copy is independent.
When a template includes a workspace agent, Rills reuses an existing compatible agent when possible. If an agent with the same name has an incompatible input or output contract, Rills creates a separate copy instead. Review the installed agents in Agents before changing a workflow that depends on them.