Update Invent trigger management documentation (TSP-1322)

build/agents/build-your-agent/triggers.mdx

@@ -49,16 +49,21 @@
 
 Active triggers display with a standard appearance, while paused triggers show a visual indicator so you can quickly see which triggers are currently active and which are paused.
 
+### Managing triggers with Inventor
+
+On Enterprise plans, you can ask [Inventor](/build/invent/invent) to enable or disable individual triggers conversationally. This is an alternative to using the UI controls — useful when you're already working in Inventor and want to adjust trigger states without switching context.
+
 ### Where to manage triggers
 
 You can pause and resume triggers from two locations:
 
 - **Agent settings**: Navigate to your agent and open the Triggers section
 - **Agent builder sidebar**: Access trigger controls directly while building your agent
+- **Inventor** (Enterprise only): Ask Inventor to enable or disable individual triggers conversationally
 
 ### Common use cases for pausing triggers
 
 - **Testing**: Pause production triggers while testing changes to your agent
 - **Maintenance**: Temporarily disable triggers during system updates or configuration changes
 - **Cost control**: Pause high-volume triggers during periods when you don't need them active
 - **Debugging**: Isolate specific triggers to troubleshoot issues
@@ -68,7 +73,7 @@
 
 ### Integration triggers
 
 We have 1,000+ integrations you can connect to and set up to trigger your Agent, including external triggers like Zapier.
 
 <Card title="Integration triggers" href="/build/agents/build-your-agent/agent-triggers/integrations">View all available integration triggers and premium options.</Card>
 
@@ -80,7 +85,7 @@
 
 ### Build your own triggers
 
 Connect to custom webhooks, APIs, and SDKs to trigger your Agent programmatically.
 
 <Columns cols={2}>
   <Card title="Webhook" href="/build/agents/build-your-agent/agent-triggers/custom-webhook">Trigger your Agent from a custom webhook.</Card>
@@ -96,7 +101,7 @@
 | React to emails, Slack messages, or CRM updates | **Integration Triggers** |
 | Run a report every morning or weekly | **Scheduled Triggers** |
 | Send follow-ups or reminders at a future time | **Scheduled Messages** |
 | Connect a third-party service like Zapier | **Integration Triggers** (external) |
 | Receive data from my own app or website | **Webhook Trigger** |
 | Trigger my Agent over HTTP from any language | **API Trigger** |
 | Build a JavaScript or TypeScript app on top of my Agent | **JavaScript SDK** |

build/invent/invent.mdx

@@ -36,13 +36,23 @@
     Get a recommendation on tool vs. agent vs. workforce based on your use case.
   </Card>
   <Card title="Build and improve evals" icon="flask-vial" href="/build/agents/build-your-agent/evals">
     Diagnoses errored logs and tools, explains why a run failed, and proposes how to fix it — so you can build stronger evals.
   </Card>
   <Card title="Log bugs to engineering" icon="bug-slash">
     When Inventor hits a platform issue it can't fix, it logs a bug to our engineering team on your behalf.
   </Card>
+  <Card title="Enable or disable agent triggers" icon="toggle-on">
+    Ask Inventor to turn individual agent triggers on or off conversationally — without navigating to the Triggers section of the agent builder.
+  </Card>
+  <Card title="Enable or disable workforce auto-triggers" icon="network-wired">
+    Toggle workforce-level auto-triggers via Inventor. The workforce must be published before Inventor can manage its trigger states.
+  </Card>
 </CardGroup>
 
+<Info>
+  Triggers created via Inventor now correctly display as "active" immediately after creation.
+</Info>
+
 <Warning>
   Inventor can log bugs on your behalf. These go to our engineering team, not support, so you won't receive updates on their progress.
 </Warning>
@@ -122,7 +132,7 @@
 ## How to use Inventor
 
 <div style={{ width:"100%",position:"relative","padding-top":"44%"}}>
 <iframe src="https://app.supademo.com/embed/cmq65ouq340ajqm6u2uly8nst?embed_v=2" frameBorder="0" title="How to use Invent" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
 </div>
 
 <Warning>

build/workforces/build-an-ai-workforce/add-triggers.mdx

@@ -40,11 +40,11 @@
 - Monthly analytics and summaries
 - Periodic system checks and maintenance tasks
 
 #### External Triggers (Zapier)
 
 External triggers like Zapier are configured and managed outside of Relevance AI. In Zapier, you can use the "Message Workforce" event to send data to your Workforce whenever a Zap fires — connecting your Workforce to any app or service that Zapier supports without needing a native integration in Relevance AI.
 
 Since Zapier triggers are managed entirely within Zapier's platform, refer to Zapier's documentation for setup and configuration of specific Zaps.
 
 ## Adding Triggers to Your Workforce
 
@@ -92,7 +92,7 @@
 
 ### Recurring Schedule Trigger Configuration
 
 Recurring schedules can be configured using either simple schedule options or advanced cron expressions:
 
 #### Simple Schedule Options
 
@@ -103,15 +103,15 @@
 | **Monthly** | Runs on chosen dates each month | Monthly reports, regular maintenance |
 | **Custom** | Runs on specific dates you select | One-off tasks or irregular schedules |
 
 #### Advanced: Cron Expressions
 
 For more precise control over scheduling, you can use **Cron expressions**. Relevance AI uses **AWS EventBridge cron format**, which requires **six fields**:
 
 ```
 minute hour day-of-month month day-of-week year
 ```
 
 **Cron Expression Format:**
 
 | Field | Values | Wildcards |
 | --- | --- | --- |
@@ -133,7 +133,7 @@
 - `W` - nearest weekday
 - `#` - nth occurrence of a day in a month
 
 **Common Cron Expression Examples:**
 
 ```
 0 10 * * ? *        # Every day at 10:00 AM
@@ -149,7 +149,7 @@
 ```
 
 <Note>
 AWS EventBridge cron expressions use 6 fields, unlike traditional Unix cron which uses 5 fields. Always include the year field, and use `?` for either day-of-month or day-of-week when specifying the other.
 </Note>
 
 ## Pausing triggers
@@ -157,7 +157,7 @@
 ### Pause all triggers
 
 <div style={{ width:"100%",position:"relative",paddingTop:"56.25%"}}>
 <iframe src="https://app.supademo.com/embed/cmlq00tfh1z7gegrdbvz0ok0e?embed_v=2" frameBorder="0" title="How to pause all triggers" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
 </div>
 
 The "Pause all triggers" feature allows you to temporarily stop integrated triggers in your workforce without disconnecting integrations or deleting trigger configurations. This feature is accessible from the workforce interface and provides a quick way to control automated workflow execution.
@@ -176,6 +176,14 @@
 Manual triggers like "user message received" are designed to always remain active and cannot be paused. This ensures users can always interact with the workforce, even when integrated triggers are paused.
 </Note>
 
+### Managing workforce triggers with Inventor
+
+On Enterprise plans, you can ask [Inventor](/build/invent/invent) to enable or disable individual workforce auto-triggers conversationally. This is an alternative to the UI controls when you're already working in Inventor.
+
+<Warning>
+  The workforce must be published before Inventor can manage its trigger states. Inventor cannot enable or disable triggers on an unpublished workforce.
+</Warning>
+
 ## Best Practices for Using Triggers
 
 ### Strategic Trigger Placement
@@ -192,7 +200,7 @@
 
 ### Recurring Schedule Best Practices
 
 - **Start small**: Begin with one simple recurring task before setting up complex schedules.
 - **Test thoroughly**: Run your workforce manually first to ensure it works as expected.
 - **Monitor initially**: Check the first few automated runs to confirm everything works correctly.
 - **Use cron for precision**: When you need exact timing control, use cron expressions instead of simple schedules.