Answer: Claude Code scheduled tasks can be triggered by GitHub events in three categories: Pull request, Release, and Issue. Within each category you can pick a specific action, such as `pull_request.opened`, or react to all actions in the category. Status: Confirmed Entry: tool/claude-code/integrations/github-trigger-events Revision: 2 Digest: sha256:b137389be6ed2e29 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:32Z Last changed: 2026-11-20T12:24:31Z (Example specific action: — → pull_request.opened) Last verified: 2026-11-20T12:24:31Z Next check: 2026-11-21T12:24:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Event category 1 | Pull request | [1] | 2026-11-20 Event category 2 | Release | [1] | 2026-11-20 Event category 3 | Issue | [1] | 2026-11-20 Example specific action | pull_request.opened | [1] | 2026-11-20 Sources: [1] Anthropic. "Automate work with scheduled tasks". https://code.claude.com/docs/en/routines.md Role: primary. Accessed: 2026-11-20T12:24:31Z Quote: "| Pull request | A PR is opened, closed, assigned, labeled, synchronized, or otherwise updated |" (Supports: Event category 1) Quote: "| Release | A release is created, published, edited, or deleted |" (Supports: Event category 2) Quote: "| Issue | An issue is opened, edited, closed, reopened, labeled, assigned, or otherwise updated |" (Supports: Event category 3) Quote: "such as `pull_request.opened`" (Supports: Example specific action) Published: 2026-11-20T02:51:59Z Snapshot SHA-256: 9377bc3e62c3bed0f909f35a4dedffee77fb9250f8d02f0650333901aa97c0e3 (captured 2026-11-20T12:24:28Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:24:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:24:31Z Last attempt: 2026-11-20T12:24:31Z Notes and limitations: Extracted automatically from a single official source (section "Supported events"). Related: https://latestn.com/tool/claude-code/integrations/gitlab-bedrock-google-cloud How do I configure Claude Code to use Amazon Bedrock or Google Cloud in GitLab CI/CD? https://latestn.com/tool/claude-code/integrations/gitlab-cicd-setup How do I set up Claude Code with GitLab CI/CD? https://latestn.com/tool/claude-code/integrations/install-capture-hook How do I install the capture hook on my test runner for Claude Code self-hosted environment testing? https://latestn.com/tool/claude-code/integrations/github-actions-cloud-provider-input How do I configure Claude Code GitHub Actions to use Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry instead of the Claude API? https://latestn.com/tool/claude-code/integrations/github-actions-cloud-provider-prerequisites What prerequisites do I need before setting up Claude Code GitHub Actions with a cloud provider? https://latestn.com/tool/claude-code/integrations/github-actions-oidc-cloud-setup How do I set up OIDC authentication so Claude Code GitHub Actions can access my cloud provider without storing long-lived credentials? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:24:31Z | changed | Example specific action: — → pull_request.opened | [1] 2026-11-20T12:24:31Z | changed | Specific action example: pull_request.opened → — | [1] 2026-11-13T03:05:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/integrations/github-trigger-events/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/integrations/github-trigger-events POST: https://latestn.com/dispute/tool/claude-code/integrations/github-trigger-events with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/integrations/github-trigger-events?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Which GitHub events can trigger a Claude Code scheduled task? Revision 2, last verified 2026-11-20T12:24:31Z. https://latestn.com/tool/claude-code/integrations/github-trigger-events (accessed 2026-11-21T09:50:34Z). @misc{LatestN_tool_claude_code_integrations_github_trigger_events_r2, title = {Which GitHub events can trigger a Claude Code scheduled task?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/integrations/github-trigger-events}}, note = {Revision 2; digest sha256:b137389be6ed2e29; last verified 2026-11-20T12:24:31Z; accessed 2026-11-21T09:50:34Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/integrations/github-trigger-events