Triggers

​

What are triggers?

A Trigger is an event that automatically starts an Agent, transforming it from an on-demand tool into a proactive agent running in the background. You can set up Triggers to run Agents based on a schedule, specific events in your other software, or incoming webhooks.

​

How to create triggers

​

Based on a schedule

This trigger runs an Agent on a recurring, time-based interval. You can set it to run hourly, daily, weekly, or monthly. Example: An Agent could run every morning at 8 AM, scan your calendar for the day’s meetings, gather recent news and background information on the attendees and their companies, and deliver a concise briefing document.

​

Based on events

This trigger runs an Agent automatically when a specific event occurs in one of your connected systems. This allows you to automate workflows in response to real-time business activities. When you create an event-based trigger, you define what starts the Agent, where it happens, and under what conditions. The configuration options are:

• Source: The connected application where the event originates (for example, Gong, Salesforce, HubSpot, or Slack).
• Trigger when: The specific event that starts the Agent, such as “New call recording”, “Deal stage changed”, or “New message in channel”.
• Filter conditions (optional): Rules that control precisely when the Agent runs.
  • If: Set conditions based on data within the event. For example, only run the Agent if a call’s duration is longer than 10 minutes.
  • Folder: Restrict the trigger to a specific folder within the source application.

Example: Analyze a Gong call transcript Goal: Automatically summarize every new sales call, identify mentioned competitors, and extract action items.

• Source: Gong
• Trigger when: New call recording
• Agent action: The Agent receives the call transcript, summarizes it, searches for competitor names against a predefined list, and sends a summary with action items to a specific Slack channel.

Example: Automate CRM updates Goal: When a deal is marked as “Closed Won” in Salesforce, automatically fill in a “Win Reason” field based on recent call notes and emails.

• Source: Salesforce
• Trigger when: Deal stage changed
• Filter: If Stage equals Closed Won
• Agent action: The Agent gathers context from recent activities, generates a concise “Win Reason”, and updates the corresponding field in Salesforce.

​

Based on a webhook

This trigger runs an Agent when it receives an HTTP request from an external system. This is a powerful way to integrate with internal tools or any third-party platform that can send webhooks, even if it doesn’t have a direct integration with Realm. To set up a webhook trigger:

1. Select trigger type: Choose “Based on a webhook” when creating your trigger.
2. Copy the webhook URL: Realm will generate a unique URL for this trigger. Copy this URL.
3. Configure the external system: Paste the copied URL into the webhook configuration section of the external tool you want to trigger the Agent from.
4. Choose authentication (optional): Select an authentication method to secure your webhook and ensure only authorized systems can trigger your Agent.

Example: A “Contact Us” form on your website could send a webhook to Realm for each new submission. An Agent could then analyze the submission, create a new lead in your CRM, and notify the appropriate sales representative in Slack.

​

Run history and monitoring

You can monitor a trigger from the Agents > Triggers list and from the trigger’s detail page. In the list view, each trigger shows its Last run and Status, which makes it easy to scan whether a trigger is active and when it last ran.

​

Trigger details page

On the trigger detail page, the Execution history section shows individual runs for that trigger. Each run includes the run time, the trigger type shown as Scheduled run, and a Completed status.

​

What you can see

• Trigger status in the list view, such as Active
• Last run in the list view
• Execution history on the trigger detail page
• Run status for each execution, such as Completed

​

Why it is useful

Use run history to:

• Confirm that a trigger is firing as expected
• Check when the trigger last ran
• Review whether recent executions completed successfully
• Track trigger activity over time

​

Monitoring tips

• After creating a trigger, check its Status and Last run in the list view to confirm it is active and running
• Open the trigger detail page to review Execution history
• Use the history table to verify that scheduled runs are completing as expected

​

Troubleshooting a trigger

If a trigger does not run as expected:

• Confirm the trigger is enabled
• Check that the trigger conditions are correct
• Verify that the source system is sending the event or webhook
• Review the most recent run history for errors or skipped runs

Run history gives you visibility into how your Agents behave over time, making it easier to monitor, debug, and trust automated workflows.