New Twilio SMS Notification Channel to stay informed about application status

Valerio Barbera

Hi, I’m Valerio software engineer from Italy, and CTO at Inspector.

I am really happy to announce the general availability of our brand new “Twilio – SMS” notification channel.

If you are a busy developer you now have one more option to intelligently forward your notificiations directly in your smartphone, stay informed about your application status, and sleep better at night.

How Twilio Notification Channel Works

We decided to implement this integration in a way that Inspector will connect to your Twilio account on your behalf, so you can keep total control about your credit spent to forward SMS to your mobile number.

We thought carefully about the option to use directly our Twilio account, but we should have revised our rates making them more difficult to understand. Furthermore you could have an existing Twilio account that allows you to access a more convenient price.

Configuration

You need three mandatory parameters from your Twilio console:

  • Account SID
  • Auth Token
  • From number

You can find these information directly in your Twilio console: https://www.twilio.com/console.

As recipients you can add as many phone numbers you want to receive selected notifications. Separate each number with a comma ( , ), but consider that each number will receive a separate SMS, so each of them contributes to the consumption of your Twilio credit.

For a more complete overview you can rely on our official documentation at: https://docs.inspector.dev/notifications/twilio-sms

Conclusion

If you are an Inspector user I hope you can find this new channel useful. We continue to make decisions trying to help as many developers as possible to monitor their code execution effortlessly with the easiest Code Execution Monitoring system out there.

If you don’t know Inspector yet, you can learn more about its Code Execution Monitoring system for PHP and Nodejs on our website: https://inspector.dev

Related Posts

The Neuron Facade: Talking to Your AI Agent in Laravel

Before this release, using Neuron AI inside Laravel meant creating a dedicated agent class, extending Agent, implementing a provider() method, and wiring the system prompt yourself. That pattern is the right one once your agent has a personality, a set of tools, and a role in your application. But it is a lot of ceremony

LLM Provider Fallback in PHP: Automatic Failover in Neuron AI Router

When I published the first article about the Neuron AI Router, I expected questions about routing rules. Which rule to use for structured output, how to write a custom one, how the round robin behaves under load. Some of those questions arrived, but the most frequent one was different, and it wasn’t really about routing