GitHub Actions Workflow Failure Text: Notify the Whole Team, Not Just the Creator

No. GitHub Actions ships email and chat (Slack, Teams) notifications, not SMS. To send SMS from a GitHub Actions workflow, point a send-mail step at an email-to-SMS gateway like TextBolt. Add the gateway address +1[phone]@sendemailtotext.com as a recipient in any standard send-mail action (dawidd6/action-send-mail or similar) inside if: ${{ failure() }}, and the failure email becomes an SMS from your registered 10DLC business number.

Per the GitHub Docs, “notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow.” This is a long-standing pain point with active community demand (discussion #55379) and no GitHub-shipped fix. TextBolt closes the gap by sitting on top of any email recipient list, including a team distribution alias.

Add a send-mail step to the workflow inside if: ${{ failure() }} with the TextBolt gateway address (+1[phone]@sendemailtotext.com) as a recipient, alongside or instead of the team distribution alias. The on-call engineer’s phone gets an SMS regardless of who last edited the workflow file or triggered the run. Use a reusable workflow at .github/workflows/notify-failure.yml to apply the same recipient across every workflow in the org.

Yes. TextBolt is a gateway email address, not an SMS API. There is no Twilio Account SID, no Auth Token, no Account credentials to store as GitHub Secrets. The gateway address itself isn’t sensitive; store it as a regular workflow vars entry if you prefer to centralize it. The send-mail step’s SMTP credentials are the only secret involved, and most teams already have those for their existing email notifications.

Yes. Define the SMS recipient once in a reusable workflow (workflow_call) at .github/workflows/notify-failure.yml or in a composite action. Every workflow that calls it inherits SMS-to-team automatically. Apply at the org-level shared workflow tier so every repository benefits with no per-repo configuration. Matrix jobs, scheduled workflows, and workflow_run-triggered workflows all use the same gateway pattern.

PagerDuty, Opsgenie, Zenduty, Better Stack, Grafana OnCall, and Rootly are full on-call management platforms with rotation engines, escalation policies, post-mortems, and integrations across the SRE stack. They’re the right fit when on-call engineering is a formal program. TextBolt covers a different, lighter job: just the SMS-to-team hop for the workflow failure. The two approaches each cover different SMS jobs and tend to be picked alongside, not instead of, TextBolt: small engineering teams pick TextBolt; mature SRE programs pick an on-call platform and may still use TextBolt for the lighter notification surface.

Yes. TextBolt registers your sender identity with The Campaign Registry as part of onboarding, so SMS sent from GitHub Actions through TextBolt routes through carrier-approved 10DLC infrastructure. This satisfies FCC business SMS requirements. Carrier 10DLC approval typically takes 1-2 business days, separate from the 30-minute hands-on setup. TextBolt is not HIPAA compliant; healthcare prospects with PHI requirements should contact sales for Enterprise options.

Yes. When the engineer texts back to acknowledge the page or escalate, the reply arrives as an email in the inbox of the original send-mail step’s sender (or the team distribution alias, depending on how the From address is configured). The team lead and platform team see acknowledgment in the same email thread the workflow failure email started. No webhook, no GitHub App configuration.

Yes. Standard plan ($49/month) and Professional plan ($99/month) include multi-user access for up to 10 team members on a shared TextBolt account. The on-call rotation, release engineers, platform team, and engineering leads share one account and one toll-free business number. No per-seat fees inside the 10-engineer cap. Enterprise plans support custom team sizes for larger organizations.

About 30 minutes of hands-on configuration: TextBolt account creation, toll-free number selection, and adding the gateway address to a send-mail step (or to a reusable workflow). Carrier 10DLC business verification runs in parallel and typically takes 1-2 business days. Once your number is approved, the on-call team gets a workflow failure SMS the next time a job fails.

Basic plan starts at $29/month for 500 SMS credits and a single user. Standard plan is $49/month for 1,000 credits with multi-user access for up to 10 team members on a shared account. Professional plan is $99/month for 2,500 credits with the same 10-user shared access. Enterprise plans cover 5,000+ credits with custom team sizes. There is a one-time $45/year setup fee for the toll-free business number. Annual plans include a 20% discount.