activate_schedule
Trigger a specific workflow schedule by its ID using the AYX-MCP-Wrapper server, enabling automated execution of workflows as per predefined configurations.
Instructions
Activate a schedule by its ID
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| schedule_id | Yes |
Implementation Reference
- src/mcp_server.py:319-322 (registration)Registration of the 'activate_schedule' MCP tool using @self.app.tool() decorator, which delegates execution to self.tools.activate_schedule(schedule_id: str). This is part of the register_tools() method.@self.app.tool() def activate_schedule(schedule_id: str): """Activate a schedule by its ID""" return self.tools.activate_schedule(schedule_id)
- src/tools.py:630-653 (handler)Core implementation of activate_schedule in AlteryxTools class. Fetches the current schedule, constructs an UpdateScheduleContract with enabled=True preserving other fields, updates the schedule via the schedules_api, and returns formatted response.def activate_schedule(self, schedule_id: str): """Activate a schedule by its ID""" try: schedule = self.schedules_api.schedules_get_schedule(schedule_id) if not schedule: return "Error: Schedule not found" contract = server_client.UpdateScheduleContract( workflow_id=schedule.workflow_id, owner_id=schedule.owner_id, iteration=schedule.iteration, name=schedule.name, comment=schedule.comment, priority=schedule.priority, worker_tag=schedule.worker_tag, enabled=True, credential_id=schedule.credential_id, time_zone=schedule.time_zone, questions=schedule.questions, ) api_response = self.schedules_api.schedules_update_schedule(schedule_id, contract) return pprint.pformat(api_response) except ApiException as e: return f"Error: {e}"