Skip to main content

What are Automations?

Automations are scheduled jobs that run Sight AI’s agent engines on your behalf. Instead of manually accepting opportunities one by one, an automation reads your queues, decides what to act on, and dispatches real work — article generation, content refreshes, internal links, site audits, outreach pitches, and more. Open Automations in the left sidebar (app.trysight.ai/automations) to create, schedule, and monitor them for the active site.
Included on Pro and Advanced. Every automation run draws from your plan’s AI credits — the same pool used for article generation, AI visibility checks, and agent chat.

Automations vs. Autopilot

Sight AI has two complementary automation systems. Most teams use both.
AutopilotAutomations
TriggerFixed daily schedule from a keyword poolOpportunity queues + your cron schedule
Input90 auto-researched keywordsSearch Opportunities, AI Prompt Opportunities, Outreach Opportunities, site health signals
OutputNew articles onlyArticles, refreshes, interlinks, audits, outreach emails
Best forSteady baseline content productionActing on real performance and visibility signals
Learn how Autopilot works →

Two types of Automations

Template automations (specialist agents)

Six proven agent engines ship as ready-made templates:
TemplateWhat it does
Search Opportunity AgentCreates articles for Search Content Gap opportunities
AI Opportunity AgentCreates articles for AI Prompt gaps
Article Boost AgentRefreshes rising or underperforming pages
Interlinking AgentInserts internal links from suggested opportunities
Site Performance AgentRuns Lighthouse and writes a prioritized fix report
Outreach AgentSends personalized outreach and triages replies (Advanced only)
Pick a template, set a schedule, optionally add guidance, and enable it.

Custom automations

Build your own automation from Sight AI’s full agent tool catalog — analytics, keywords, articles, opportunities, indexing, inbox, and more. You write the instructions; Sight AI runs them on a schedule with the tools you allow. Build a custom automation →

How every run works

Every automation run follows the same pattern:
  1. Pull — read the relevant queue or data source (opportunities, articles, inbox, etc.)
  2. Dedup — skip rows that already have articles, were handled recently, or fail eligibility checks
  3. Act — call the configured tools (dispatch article, refresh, insert anchor, send pitch, etc.)
  4. Record — write a per-run summary with every tool call so you can audit what happened
Template automations have constrained tool surfaces by design — the Interlinking Agent can insert anchors but cannot create new articles, for example.

Where Automations get their work

SourceAutomation that consumes it
Search Opportunities → Content GapSearch Opportunity Agent
Search Opportunities → Refresh / RisingArticle Boost Agent
Search Opportunities → InterlinksInterlinking Agent
Content Opportunities (AI)AI Opportunity Agent
Site health signalsSite Performance Agent
Outreach OpportunitiesOutreach Agent (+ Inbox for replies)
You can mix manual and autonomous workflows — accept some opportunities yourself, let automations work through the rest.

Plan availability

PlanAutomationsOutreach Agent
Starter
ProIncluded (credit-metered)
AdvancedIncluded (credit-metered)Included
See Plans and Pricing →

Safety and cost controls

Automations are conservative by default:
  • Action budgets cap how many real actions a single run can take (template automations)
  • Tool-call budgets cap total LLM steps per run (custom automations, up to 15 steps)
  • Schedule throttling — runs are evaluated every 15 minutes; each automation fires at most once per window
  • Site eligibility — automations won’t run against unlicensed or paused sites
  • Credit checks — runs are blocked when your team has no AI credits remaining

Next steps

Getting Started

Create your first automation in minutes

Agent Templates

Deep dive on each specialist agent

Custom Automations

Build tool-based workflows from scratch

Monitoring & Troubleshooting

Activity logs, notifications, and common fixes