> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt > Use this file to discover all available pages before exploring further. # Triggers in Agents > Start Agent runs automatically on a schedule, an app event, a change on the web, or a change in your Profound data A run trigger starts an Agent run automatically when its condition is met. The condition can be a schedule, an event in a connected app or on the web, or a change in your Profound data. Add triggers in the Agent's settings panel, or ask Aim in the Agent's chat to add them. ## Trigger types | Trigger | Runs when | Example | | - | - | - | | **Schedule** | A scheduled time arrives | Every Monday at 9:00 AM | | **App** (listed by app name, for example **Slack**) | An event happens in a connected app | A new message is posted in a Slack channel | | **Monitor** | Something changes on the web | A competitor publishes a new blog post | | **Profound data** | A Profound metric meets a condition | Visibility Score drops 10% compared with the last 7 days | Add more than one trigger to an Agent, and it runs when any trigger's condition is met. By default, an Agent has no triggers and runs only when you select **New run**. ## How triggers behave * **One switch turns triggers on and off.** The switch next to **Run triggers** in the settings panel pauses or resumes all of the Agent's triggers at once. It appears once the Agent has at least one trigger. Only the person who created a trigger can switch it. * **Triggered runs use the current version of the Agent.** Changes you make apply to the next triggered run. * **Triggers belong to the person who set them.** Only that person sees the triggered run and its outputs. People the Agent is shared with can run it themselves and see their own runs. Triggers aren't saved in version history. * **Every triggered run is a chat.** Find it under **Run history** at the top of the Agent's page, with any outputs under **Artifacts**. * **Triggered runs can run Workflows, too.** If the Agent's instructions include a Workflow, a triggered run runs it and uses its results, the same as a manual run. The person who set the trigger needs access to the Workflow. ## Add a schedule In the settings panel, select **Add** next to **Run triggers** and point to **Schedule**. Select **Hourly**, **Daily**, or **Weekly** to add a schedule that starts now, or **Custom** to set it up yourself: 1. Set **Starts on** to the first date and time the Agent should run. 2. Choose a **Frequency**: **Doesn't repeat**, **Daily**, **Weekdays**, **Weekend**, **Weekly**, **Monthly**, **Annually**, or **Custom**. For a custom cadence, select **Custom**, set **Repeat every** (for example, 1 week or 4 hours), and select the days under **Repeat on**. 3. Select **Add trigger** to save. The trigger appears under **Run triggers**, named after how often it runs, for example, "Every Monday at 9:00 AM". Select it to edit it, or select **Remove** in the dialog or the trash icon next to it to delete it. To add a schedule in the chat, ask Aim, for example, "Run this Agent every Monday at 9 AM." ## Add an app trigger 1. Select **Add** next to **Run triggers** and point to the app, for example **Slack**. Only connected apps that support triggers appear in the menu. 2. Choose the event, for example **New channel message** or **Reaction added to a message**. 3. Complete the trigger sentence: for Slack, choose which messages or reactions count and select the channel. The trigger saves as soon as the sentence is complete. For the Slack app trigger, add the Profound Slack app to the channel you want to use with an Agent. The channel list only shows channels the app has already joined. Learn more in [Connect Slack to Profound](/integrations/slack/connect-slack-to-profound). ## Add a monitor A monitor watches the web for updates that match a query you write. Profound checks for new matches on the schedule you choose, ignores anything it has already reported, and starts a run only when something new appears. 1. Select **Add** next to **Run triggers** and choose **Monitor**. 2. Optionally, enter a **Name**, for example "Competitor blog monitor". If you leave it empty, the monitor is named "Monitor 1", "Monitor 2", and so on. 3. In the **Query** field, describe what to watch (up to 2,000 characters), for example, "a new post on competitor.com/blog" or "changes to the pricing page at competitor.com/pricing". 4. Choose a **Frequency**: **Every hour** (the default), **Every 2 hours**, **Every 4 hours**, **Every 6 hours**, **Every 12 hours**, or **Every day**. 5. Select **Add trigger** to save. After you save a monitor, you can rename it, but you can't change the query or frequency. To change them, remove the monitor and add a new one. ### Writing a good monitor query * Describe what you're looking for in plain language, the way you'd brief a colleague. * Keep your query clear and specific: include what to watch for and where to watch for it. * Leave out date ranges. The monitor already surfaces only what's new. Prefer the queries in the first column and avoid the ones in the second. | Prefer ✅ | Avoid ❌ | | - | - | | AI startup funding announcements | Find all AI funding news from the last 2 years | | Tesla news and announcements | Tesla news after December 12, 2025 | | New blog posts published on competitor.com | competitor.com blog | ## Add a Profound data trigger 1. Select **Add** next to **Run triggers** and choose **Profound data**. 2. Choose the **Category** and the **Asset** to watch. 3. Build the **Trigger** condition: set **When** a metric **drops by**, **rises by**, **drops below**, or **rises above** a value (in % or a number), **Against** a comparison window (**Last day**, **Last 7 days**, **Last 14 days**, **Last month**, or **Last 3 months**). 4. Narrow the scope with **Filters**: Topics, Platforms, Regions, Tags, or Personas. 5. Set the **Check frequency** (**Daily** by default, or **Weekly**, **Bi-weekly**, or **Monthly**) and select **Add trigger**. Available metrics: * **Visibility**: Visibility Score, Share of Voice, Average Position, and their ranks. * **Sentiment**: positive percentage, negative percentage, and assessment count. * **Citations**: Citation Share, citation count, Citation Rank, and Citation Coverage. * **FactCheck**: Accuracy score, and inaccurate, accurate, and verified claim counts. These appear only when FactCheck is set up for the category. ## Edit, pause, or remove a trigger In the Agent's settings panel, select the trigger under **Run triggers**. Change the settings and select **Save**, or select **Remove** to delete the trigger. To pause all of an Agent's triggers without deleting them, turn off the switch next to **Run triggers**, and turn it back on to resume. To stop an Agent from running on its own permanently, remove its triggers. Trigger changes apply right away.