Skip to main content

Calling your Agent on-demand

Specialized Agents can be quickly called in Coworker or Slack whenever you need hem.

Overview

In addition to running on a schedule or waiting for an event trigger, Coworker Agents can be called on-demand β€” triggered instantly from Work chat or Slack whenever you need them. To use on-demand triggers, the appropriate trigger options must be enabled in your Agent's settings.


Calling an Agent from Work Chat

You can invoke any Agent directly from Coworker's Work chat interface by mentioning it with @.

  1. Navigate to the Work page

  2. In the chat input, type @ followed by your agent's name

  3. Select your agent from the list that appears and press Enter

  4. Optionally, include a message or question after the mention to pass context to the agent

Prerequisite: The When agent is @ mentioned in Coworker trigger must be enabled on your Agent for this to work. You can enable it from the Triggers section in Agent Builder.


Calling an Agent from Slack

If your organization uses the Coworker Slack integration, you can trigger agents directly from any Slack channel or DM using the following format:

@Coworker +agent-name

For example: @Coworker +weekly-pipeline-digest

Prerequisite: The Slack mention trigger must be enabled on your Agent. You can enable it from the Triggers section in Agent Builder. Also ensure the Coworker Slack app is installed in your workspace β€” if not, invite it with /invite @Coworker.


Enabling On-Demand Triggers

To enable either on-demand trigger for an Agent:

  1. Go to Agents and open the agent you want to configure

  2. Click Edit to open the Agent Builder

  3. Navigate to the Triggers section

  4. Enable one or both of the following:

    • When agent is @ mentioned in Coworker β€” allows calling the agent from Work chat

    • Slack mention β€” allows calling the agent via @Coworker +agent-name in Slack

  5. Save your Agent

Note: At least one trigger must be enabled when saving an Agent. If only the Slack mention trigger is selected, be sure another trigger type is also enabled or the Agent may not save correctly.

Did this answer your question?