> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/automate.md). # Automate - [Monitors](https://docs.groundcover.com/automate/monitors.md) - [Create a new Monitor](https://docs.groundcover.com/automate/monitors/create-a-new-monitor.md) - [Issues page](https://docs.groundcover.com/automate/monitors/issues-page.md): View and analyze monitor issues with detailed timelines, metadata, and context to quickly identify and resolve problems in your environment. - [Monitor List page](https://docs.groundcover.com/automate/monitors/monitor-list-page.md): View, filter, and manage all monitors in one place, and quickly identify issues or create new monitors. - [Notification Routes](https://docs.groundcover.com/automate/monitors/notification-routes.md): Notification Routes let you automatically send notifications to Destinations when monitor issues change state. - [Silences page](https://docs.groundcover.com/automate/monitors/silences-page.md): Manage and create silences to suppress Monitor notifications during maintenance or specific periods. Use one-time silences for ad-hoc needs, or recurring silences for scheduled maintenance windows tha - [Monitor Catalog page](https://docs.groundcover.com/automate/monitors/monitor-catalog-page.md): Explore and select pre-built Monitors from the catalog to quickly set up observability for your environment. Customize and deploy Monitors in just a few clicks. - [Monitor YAML structure](https://docs.groundcover.com/automate/monitors/monitor-yaml-structure.md) - [SQL Based Monitors](https://docs.groundcover.com/automate/monitors/sql-based-monitors.md) - [Migrating from Issues to Monitors Issues Page](https://docs.groundcover.com/automate/monitors/migrating-from-issues-to-monitors-issues-page.md) - [Workflows](https://docs.groundcover.com/automate/workflows.md) - [Create a new Workflow](https://docs.groundcover.com/automate/workflows/create-a-new-workflow.md) - [Workflow Examples](https://docs.groundcover.com/automate/workflows/workflow-examples.md) - [Integration Examples with Workflows](https://docs.groundcover.com/automate/workflows/integration-examples.md) - [Full Webhook Examples](https://docs.groundcover.com/automate/workflows/full-webhook-examples.md) - [incident.io](https://docs.groundcover.com/automate/workflows/full-webhook-examples/incident.io.md) - [MS Teams](https://docs.groundcover.com/automate/workflows/full-webhook-examples/ms-teams.md) - [Slack App for Channel Routing](https://docs.groundcover.com/automate/workflows/full-webhook-examples/slack-app-for-channel-routing.md) - [Alert Structure](https://docs.groundcover.com/automate/workflows/alert-structure.md): Fields description in the alert you can use in your workflows - [Agent Mode](https://docs.groundcover.com/automate/agent-mode.md): AI-powered assistant for investigating, exploring, and building with your groundcover data - [Requirements & Compatibility](https://docs.groundcover.com/automate/agent-mode/requirements.md): Deployment types and prerequisites for using Agent Mode - [Getting Started](https://docs.groundcover.com/automate/agent-mode/getting-started.md): Learn how to interact with groundcover Agent Mode - [Skills](https://docs.groundcover.com/automate/agent-mode/skills.md): Teach the Agent your team's workflows, runbooks, and conventions with custom Skills - [Example Prompts](https://docs.groundcover.com/automate/agent-mode/example-prompts.md): Ready-to-use prompts for common investigation, exploration, and creation scenarios - [Configuring Settings](https://docs.groundcover.com/automate/agent-mode/configuring-settings.md): How to configure Agent Mode access, LLM providers, models, instructions, and budgets for your workspace - [Privacy & Security](https://docs.groundcover.com/automate/agent-mode/privacy-and-security.md): Data handling, LLM providers, tenant isolation, session management, and access control for groundcover Agent Mode - [Cost Management](https://docs.groundcover.com/automate/agent-mode/cost-management.md): Control monthly Agent Mode spending with organization, default, and per-user cost limits - [groundcover MCP](https://docs.groundcover.com/automate/groundcover-mcp.md) - [Configure groundcover's MCP Server](https://docs.groundcover.com/automate/groundcover-mcp/configure-groundcovers-mcp-server.md) - [MCP Tools Reference](https://docs.groundcover.com/automate/groundcover-mcp/mcp-tools-reference.md) - [Getting-started Prompts](https://docs.groundcover.com/automate/groundcover-mcp/getting-started-prompts.md) - [Real-world Use Cases](https://docs.groundcover.com/automate/groundcover-mcp/real-world-use-cases.md) - [Connectors](https://docs.groundcover.com/automate/connectors.md): Connectors let individual users link their external tool accounts to groundcover, enabling Agent Mode to take actions on their behalf - [Slack](https://docs.groundcover.com/automate/connectors/slack.md) - [@groundcover Agent in Slack](https://docs.groundcover.com/automate/connectors/slack/slack-agent.md): Interact with groundcover's Agent directly from Slack by mentioning @groundcover in any channel - [Linear](https://docs.groundcover.com/automate/connectors/linear.md): Connect Linear to create and manage issues from monitor incidents, notification routes, and groundcover Agent Mode - [Cursor Cloud Agents](https://docs.groundcover.com/automate/connectors/cursor.md): Connect your Cursor account to let groundcover Agent Mode run code changes on your repositories using Cursor's cloud coding agent - [Claude Managed Agents](https://docs.groundcover.com/automate/connectors/claude-managed-agents.md): Connect Claude Managed Agents to let groundcover Agent Mode run coding tasks with your configured Claude agent and environment - [Notion](https://docs.groundcover.com/automate/connectors/notion.md): Connect Notion to search workspace knowledge and publish Agent Mode findings - [Pylon](https://docs.groundcover.com/automate/connectors/pylon.md): Connect Pylon to investigate customer issues and take support actions from Agent Mode - [GitHub](https://docs.groundcover.com/automate/connectors/github.md): Connect GitHub to investigate code and manage development work from Agent Mode - [PagerDuty](https://docs.groundcover.com/automate/connectors/pagerduty.md): Connect PagerDuty to investigate and manage incidents from Agent Mode - [Rootly](https://docs.groundcover.com/automate/connectors/rootly.md): Connect Rootly to investigate incidents and coordinate response from Agent Mode - [incident.io](https://docs.groundcover.com/automate/connectors/incident-io.md): Connect incident.io to analyze operations and manage incidents from Agent Mode - [Atlassian Rovo](https://docs.groundcover.com/automate/connectors/atlassian-rovo.md): Connect Atlassian Rovo to work with Jira and Confluence from Agent Mode - [Remote MCP Servers](https://docs.groundcover.com/automate/connectors/mcp.md): Allowlist Remote MCP Servers to extend Agent Mode with custom tools and capabilities - [Notification Channels](https://docs.groundcover.com/automate/workflow-integrations.md) - [Slack](https://docs.groundcover.com/automate/workflow-integrations/slack-webhook-integration.md) - [OpsGenie](https://docs.groundcover.com/automate/workflow-integrations/opsgenie-integration.md) - [PagerDuty](https://docs.groundcover.com/automate/workflow-integrations/pagerduty-integration.md) - [Webhook](https://docs.groundcover.com/automate/workflow-integrations/webhook-integration.md) - [incident.io](https://docs.groundcover.com/automate/workflow-integrations/incident.io.md) - [MS Teams](https://docs.groundcover.com/automate/workflow-integrations/ms-teams.md) - [Jira](https://docs.groundcover.com/automate/workflow-integrations/jira-webhook-integration.md) - [Email alerts via Zapier](https://docs.groundcover.com/automate/workflow-integrations/send-groundcover-alerts-to-email-via-zapier.md) - [Destinations](https://docs.groundcover.com/automate/connected-apps.md): Destinations are external integrations you configure to receive notifications from or interact with groundcover - [Slack App](https://docs.groundcover.com/automate/connected-apps/slack-app.md) - [Slack Webhook](https://docs.groundcover.com/automate/connected-apps/slack-webhook.md) - [PagerDuty](https://docs.groundcover.com/automate/connected-apps/pagerduty.md) - [incident.io](https://docs.groundcover.com/automate/connected-apps/incident.io.md) - [Rootly](https://docs.groundcover.com/automate/connected-apps/incident.io-1.md) - [Generic Webhook](https://docs.groundcover.com/automate/connected-apps/generic-webhook.md) - [Using Predefined Variables](https://docs.groundcover.com/automate/connected-apps/generic-webhook/using-predefined-variables.md) - [MS Teams Webhook Example](https://docs.groundcover.com/automate/connected-apps/generic-webhook/ms-teams-webhook-example.md) - [Email via Zapier](https://docs.groundcover.com/automate/connected-apps/generic-webhook/email-via-zapier.md) - [OpsGenie](https://docs.groundcover.com/automate/connected-apps/opsgenie-integration.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.groundcover.com/automate.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.