Using Web Triggers with Airspeed Agents

Last updated: July 13, 2026

Web Triggers let an Airspeed Agent run when new information appears on the web that matches a monitor query you define. Use them when you want Airspeed to watch for external events and automatically summarize why they matter.

When to use a Web Trigger

Use a Web Trigger when the important signal lives outside your CRM or call data. Examples include:

  • A competitor launches a new AI product.

  • A target account announces a funding round.

  • A customer or prospect hires a new executive.

  • A company opens a new office or enters a new market.

  • A public company reports earnings or mentions a strategic priority.

  • A regulatory change affects your buyers.

Create a Web Trigger agent

  1. Go to Agents → Command Center.

  2. Click Create an agent.

  3. In Step 1: Trigger, choose Web Trigger.

  4. Write a Monitor query that describes the event Airspeed should watch for.

  5. In Step 2: Prompt, tell the agent what to do when the event is detected.

  6. Choose the output recipients in Step 3: Output.

  7. Use Test Agent, then save.

Writing a good Monitor query

The Monitor query should describe the web event you want Airspeed to detect. Keep it specific enough to avoid noise, but broad enough to catch the signal.

Good examples

  • News about competitors launching new AI sales products

  • Funding announcements for companies in our target account list

  • Executive leadership changes at enterprise cybersecurity companies

  • Regulatory updates affecting financial services call recording or compliance

Too broad

  • AI news

  • Sales updates

  • Company changes

Too narrow

  • Exact phrase from one press release that may never repeat

  • One specific URL unless you only care about that page

Use Web Trigger variables in the prompt

Web Trigger agents can use these variables:

Variable

What it inserts

{{monitor_output}}

The summary of the detected event.

{{monitor_source_urls}}

The source URLs where the event was found.

{{monitor_event_date}}

The date the event was detected.

Prompt examples

Competitor launch alert

Summarize this competitor event: {{monitor_output}}

Use these sources: {{monitor_source_urls}}

Explain what changed, why it matters for our sales team, which deals or accounts may be affected, and what talk track reps should use in active opportunities.

Target account funding alert

Review this monitored event: {{monitor_output}}

If this is a funding announcement, identify why it matters, whether the company matches our ICP, any open opportunities or prior conversations in Airspeed, and the recommended next step for the account owner.

Executive change alert

Analyze this leadership change: {{monitor_output}}

Summarize the new executive's likely priorities, any relevant account history in Airspeed, and a concise outreach angle for the account owner.

Output recommendations

Web Trigger agents often work best with generalized output to a Slack channel, because the same event may be useful to several people. For account-specific monitors, email or Slack DM to the account owner may work better.

Troubleshooting

The agent is firing too often

Narrow the Monitor query. Include the company type, region, topic, product category, or business event you care about.

The agent is not firing

Broaden the Monitor query and confirm the event is public enough to be detected from web sources.

The output is generic

Add instructions that tell the agent to connect the event back to Airspeed data, such as open deals, account owners, previous calls, competitors mentioned, or customer segments.