Source
Agent capabilities & guardrails — found from sitemap — Dust
Checked for Dust on 26 Oct 2026
- Page
- https://docs.dust.tt/docs/user-documentation/agents/triggers
- Checked
- 26 Oct 2026, 18:15 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:cafbb736b3c95c4ac0c6845ffc4d44e973ec9ae537e6468f79c80a0409c7c647
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Triggers definition Report an error
“A trigger starts an agent without anyone sending it a message. The agent runs with its usual instructions, tools, and knowledge, and each run creates a conversation you can open to see what it did.”
-
Trigger types Report an error
“Type Runs the agent Example Schedule At times you describe in plain language Every weekday at 8 AM, summarize yesterday’s new support tickets Webhook When another system sends an event When a pull request is opened on GitHub, review it”
-
Webhook sources Report an error
“Webhook triggers work with built-in sources (GitHub, Jira, Linear, Zendesk, and Fathom) or with a custom webhook from any system that can send HTTP requests.”
-
Trigger setup Report an error
“Open the agent in the Agent Builder. In the Triggers section, click Add triggers.”
-
Trigger admin requirement Report an error
“Webhook sources must first be created by a workspace admin: see Webhooks.”
-
Trigger ownership Report an error
“Triggers belong to the member who created them. Triggers that other members added to the same agent appear under Other members’ triggers in the Agent Builder.”
-
Trigger run destination Report an error
“By default, the conversation appears in your own conversation history. To share runs with your team, pick a Pod under Where to create this conversation? in the trigger settings: the conversation is then created in that Pod, where all its members can see it.”
-
Trigger credits Report an error
“Trigger runs consume credits like any other agent run. The Credits setting on each trigger decides whether your credits or the workspace’s pay for them.”
-
Webhook rate limit Report an error
“Webhook triggers run at most 42 times per 24 hours by default.”
-
Trigger management Report an error
“To review your triggers and their credit consumption, or to enable, disable, or delete them, see Review your triggers.”
Scores citing this record
- The Automation Lead Integrations, connectors & knowledge
- The Automation Lead Agent capabilities & guardrails
- The Automation Lead Pricing transparency
- The Automation Lead Integrations, connectors & knowledge
- The Automation Lead Agent capabilities & guardrails
- The Automation Lead Pricing transparency
- The Customer-Service Director Integrations, connectors & knowledge
- The Customer-Service Director Agent capabilities & guardrails
- The Customer-Service Director Pricing transparency
- The Customer-Service Director Integrations, connectors & knowledge
- The Customer-Service Director Agent capabilities & guardrails
- The Customer-Service Director Pricing transparency
- The Data Protection Officer Agent capabilities & guardrails
- The Data Protection Officer Pricing transparency
- The Data Protection Officer Integrations, connectors & knowledge
- The Data Protection Officer Agent capabilities & guardrails
- The Head of IT Agent capabilities & guardrails
- The Head of IT Integrations, connectors & knowledge
- The Head of IT Agent capabilities & guardrails
- The Skeptic Integrations, connectors & knowledge
- The Skeptic Agent capabilities & guardrails
- The Skeptic Agent capabilities & guardrails
- The Works Council Member Integrations, connectors & knowledge
- The Works Council Member Agent capabilities & guardrails
- The Works Council Member Agent capabilities & guardrails
- The Works Council Member Pricing transparency