Automating Work Beyond Code

Resources

• GitHub Actions Event Triggers — The official event reference covers repository changes, issues, comments, schedules, workflow completion, and external dispatch. Use it to choose precise entry points for observe–classify–route–execute–verify–communicate pipelines rather than making every automation poll the repository. https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

• Claude Code Hooks — Documents lifecycle events and event-specific decision outputs for blocking actions, changing tool inputs, adding context, and controlling continuation. A direct reference for push-based instructions and deterministic checks, including why a post-action hook cannot retroactively prevent an already completed side effect. https://code.claude.com/docs/en/hooks

• Slack Events API — Explains subscriptions, scopes, event delivery, acknowledgments, and retries for message-driven applications. Useful for extending agent work into communication channels while treating messages as untrusted inputs and handling duplicate deliveries explicitly. https://docs.slack.dev/apis/events-api/

• CloudEvents Specification — Defines a common event envelope with identifiers, source, type, and data. Provides a portable input contract for classification and routing across repositories, messages, and external systems; it does not itself implement authorization or exactly-once processing. https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md

• Inngest Idempotency — Shows how event and function-level idempotency prevent duplicate runs. Use it to distinguish deduplicating a pipeline invocation from making its external effects safe to retry. https://www.inngest.com/docs/guides/handling-idempotency

• Inngest Concurrency Control — Documents limits on parallel step execution and keyed concurrency. Useful for containing an event burst, protecting shared services, and preventing one tenant or workflow from consuming all execution capacity. https://www.inngest.com/docs/guides/concurrency

• Inngest Throttling — Explains throughput control over time while excess work waits to run. Gives the lesson a concrete backpressure mechanism; distinguish rate limits from monetary budgets and define what happens when queued work becomes stale. https://www.inngest.com/docs/guides/throttling

• GitHub Actions Secure Use — Covers untrusted input, script injection, token permissions, secrets, and dependency trust. Apply it to agent automations that read issues or comments before accessing privileged tools, especially when external text could redirect execution. https://docs.github.com/en/actions/reference/security/secure-use

• GitHub Deployment Environments — Documents environment protection rules, required reviewers, and controlled access to deployment secrets. Provides a concrete human checkpoint for high-impact pipeline stages, with availability depending on repository visibility and plan. https://docs.github.com/en/actions/reference/workflows-and-actions/deployments-and-environments

• Temporal Workflow Message Passing — Distinguishes Signals, Queries, and Updates for interacting with running workflows. Useful for pushing new instructions or knowledge into durable work, inspecting its state, and choosing whether a caller needs acknowledgment or a completed result. https://docs.temporal.io/encyclopedia/workflow-message-passing

• Inngest Failure Handlers — Shows how to run recovery or notification logic after a function exhausts its retries. Supports an explicit failure branch that contains damage, communicates what happened, and escalates for human action instead of silently restarting forever. https://www.inngest.com/docs/features/inngest-functions/error-retries/failure-handlers