Weave Code
Driver Nexmo Laravel Package
botman/driver-nexmo
Nexmo SMS driver for BotMan, connecting PHP chatbots to Vonage/Nexmo messaging. It handles inbound webhooks and outbound SMS so BotMan conversations can run over Nexmo. Useful for legacy integrations; adoption is minimal and maintenance activity is limited.
BotMan Nexmo Driver
Frequently asked questions about Driver Nexmo
- How do I install the BotMan Nexmo driver?
- Install the package with Composer using composer require botman/driver-nexmo. Then register the Nexmo driver in your BotMan bot configuration and point incoming Nexmo webhooks at your bot endpoint. Check the package README for the exact driver class and any service provider details.
- How do I configure Nexmo or Vonage credentials for BotMan?
- Configure your Nexmo/Vonage API credentials and SMS number in the driver configuration used by BotMan. The driver needs those credentials to send outbound SMS replies through the Nexmo API. Keep secrets in environment variables rather than committing them to source control.
- How does the Nexmo webhook work with a BotMan bot?
- Nexmo sends inbound SMS callbacks to a public webhook URL that you configure in the Nexmo/Vonage dashboard. The driver parses that request and passes the message into BotMan so your conversations and middleware can run. Your webhook route must be publicly reachable and excluded from CSRF protection where applicable.
- Does botman/driver-nexmo work with Laravel?
- Yes, it is a Composer package that can be used in Laravel applications alongside BotMan's Laravel integration. Because the driver is lightweight and maintenance is limited, verify compatibility with your installed BotMan and Laravel versions before relying on it. Test the webhook and outbound SMS flow in your own application.
- Can I build two-way SMS conversations with this BotMan driver?
- Yes, the driver supports inbound Nexmo SMS webhooks and outbound SMS replies, enabling two-way text conversations. It works with BotMan conversations and middleware, so you can use familiar BotMan messaging patterns over SMS. Keep SMS length and carrier behavior in mind when designing conversation flows.
- How can I test a Nexmo SMS bot locally?
- Expose your local webhook endpoint through a tunnel such as ngrok and configure Nexmo/Vonage to call that URL. Send test SMS messages or simulate the webhook payload to verify inbound handling, then confirm outbound replies are sent through the Nexmo API. You can also test BotMan conversation logic separately with BotMan's testing helpers.
- Is botman/driver-nexmo actively maintained?
- Adoption is minimal and maintenance activity is limited, so treat it as a legacy integration rather than a actively developed package. Review the repository history and issue tracker before adopting it for new work. For new projects, compare it with maintained SMS or Vonage integration options.
- What are alternatives to the BotMan Nexmo driver for SMS bots?
- You can use another BotMan SMS driver, such as Twilio, if it fits your provider requirements. Alternatively, write a custom BotMan driver against the current Vonage Messages API or another SMS provider. Evaluate maintenance status, webhook reliability, and provider features before choosing.
- Does this driver send outbound SMS replies through the Nexmo API?
- Yes, it sends BotMan replies back through the Nexmo API using your configured credentials and SMS number. Make sure the sending number and account permissions are correctly set in Nexmo/Vonage. Handle API errors and rate limits in your application code.
- What should I consider before using botman/driver-nexmo in production?
- Confirm that the package is compatible with your BotMan and Laravel versions, since maintenance activity is limited. Secure Nexmo credentials, protect and validate the public webhook route, and add idempotency and error handling for SMS delivery. Also consider whether a more actively maintained SMS integration is a better long-term fit.
Weaver
How can I help you explore Laravel packages today?