Templates
A template is a complete automation: a trigger, agent instructions, and actions already configured for a specific job. Templates are grouped into five categories: Observability, CI/CD, Infrastructure, Scheduled, and Platform.
Some examples from the catalog:
- Detect anomalous traffic (
detect-anomalous-traffic): fires on thealerttrigger, analyzes traffic patterns for spikes, geographic anomalies, and DDoS indicators, and makes a clear escalation decision. - Generate weekly report (
generate-weekly-report): runs on acrontrigger every Friday at 10:00 and compiles an engineering report covering issues, deployments, and pull request activity. - Babysit GitHub deployment (
babysit-github-deployment): fires ongithub.deployment, runs pre-flight checks and post-deploy health monitoring, and opens an incident with a rollback recommendation when the deploy is degraded.
Install a template
Browse the catalog and create from a slug:
polylane automation catalog
polylane automation from-template detect-anomalous-traffic
polylane automation from-template daily-aws-infrastructure-audit --pass-count 2 --provider aws
--pass-count overrides the template's number of parallel agent passes (1 to 10). --provider checks that the template targets that provider; the command fails on a mismatch.
Or from the API:
curl -X POST https://api.polylane.com/v1/automations/from_template \
-H "Authorization: Bearer <api-key>" \
-H "Content-Type: application/json" \
-d '{"workspaceId": "<workspace-id>", "templateSlug": "detect-anomalous-traffic"}'
You can also pick a template in the console under Automations → Templates.
Installing a template creates a regular automation. Everything stays editable: change the instructions, adjust filters, or add destinations. Templates that reference skills attach those skills to the new automation on install. Connect the template's providers under integrations first, so the trigger has events to act on.
Catalog
Search, filter by category or provider, and open any template to see its trigger, instructions, actions, and required providers.
Reporting
Scheduled reports, digests, and audits
Scheduled Scans
Recurring codebase and coverage scans
Security
Detect security risks and vulnerabilities
Webhook
Receive and process external events
Deployment
Monitor and validate deployments
Code Review
Review and assess pull request changes