Create scheduled, API, and event tasks¶
Open Automation and create a rule. You can also use Create scheduled task from an agent card’s additional-actions menu; check the selected agent in the form.
1. Configure execution¶
Field |
Purpose and value |
|---|---|
Name |
Identifies the rule, such as “Daily product update summary” |
Agent |
An assistant already validated for the task |
Execution model |
A model available in the workspace |
Status |
Enable when ready, or save disabled while reviewing configuration |
Trigger |
Schedule, API invocation, or event callback |
Execution instructions |
Goal, sources, scope, output format, and handling of missing information |
There is no separate output-requirements field. Include those requirements in the execution instructions.
Example:
Read the material relevant to this week’s updates in the bound product knowledge base. Produce a summary with change, impact, and source columns. List missing dates or evidence as questions to confirm. Keep the result in this run’s record.
2. Choose a trigger¶
Schedule¶
Supported choices include every minute, hourly, daily, weekly, monthly, and custom Cron. Set the corresponding time parameters and inspect the natural-language schedule and Cron expression.
For custom Cron, verify the frequency in the preview so a daily task is not accidentally configured to run every minute. If the timezone is not explicit, compare Next trigger with the intended business time before enabling an important task.
API invocation¶
Select API invocation and save the rule. Integrate with the actual API endpoint and authentication requirements supplied by the product page or deployment maintainer. The task page’s browser URL is not the API endpoint.
Send an identifiable test input and check both the request result and MOI run history. An HTTP response and completion of the agent’s business task are separate checks.
Event callback¶
Select Event callback. Incoming events are passed to the agent as user text. Explain in the execution instructions how to interpret the event, which fields to extract, and how to handle missing fields.
Configure the source connection, subscription, and receiver through the relevant tool or system. Send a test event and check that it triggers the intended rule. Creating a rule does not by itself make a third party send events.
3. Save and verify¶
Wait for submission to finish, then inspect the rule name, status, and trigger information in the list. A disabled rule can show paused or unscheduled and should not be expected to execute automatically.
If submission keeps loading or the list does not update, search for the rule name and refresh before retrying. Avoid creating duplicate rules. Once the rule exists, follow Run validation.
Edit an existing task¶
Open the rule’s edit action, review current fields, and save. An existing scheduled task’s edit form may offer only scheduled and API triggers. Use the options actually provided; do not assume every creation-time trigger can be selected during editing.