Weave Code
Driver Hangouts Laravel Package
botman/driver-hangouts
A BotMan driver for Google Hangouts that connects your chatbot to Hangouts conversations. Add Hangouts support to Laravel/PHP bots so users can interact with your bot directly through Google Hangouts.
Google Hangouts driver for BotMan
Frequently asked questions about Driver Hangouts
- How do I install the BotMan Hangouts driver with Composer?
- Install it with composer require botman/driver-hangouts, then register the driver in your BotMan configuration and expose an HTTPS webhook route for Hangouts events. Because the package is old, check Composer constraints against your PHP and BotMan versions before adding it to a real project.
- Does botman/driver-hangouts work with Laravel 10 and 11?
- It is unlikely to install cleanly on Laravel 10 or 11 without changes. The last release was in 2018, so expect Composer conflicts with modern illuminate/* packages and PHP 8.x constraints. Treat compatibility as a time-boxed spike, and be prepared to patch or fork the driver.
- Which BotMan versions is the Hangouts driver compatible with?
- The driver targets the BotMan 2.x era and should be pinned to a known-good BotMan major version. Verify the driver installs against your exact BotMan release and run a webhook round-trip test. Dependency constraint adjustments are likely for newer BotMan versions.
- Is this driver for Google Hangouts or Google Chat?
- It was built for Google Hangouts Chat, which has since been rebranded and evolved into Google Chat. API surfaces, event schemas, card formats, and threading have changed since 2018, so the driver may target older endpoints. Confirm whether your target is Hangouts Chat classic or current Google Chat before adopting it.
- Does the Hangouts driver verify Google webhook signatures or JWTs?
- The driver's signature verification behavior is not documented here, and an unmaintained 2018 package may not verify Google-signed requests at all. You should add JWT verification that validates issuer and audience before accepting any webhook event. Never expose an endpoint that accepts spoofed Hangouts events.
- Why does botman/driver-hangouts have no repository or recent releases?
- The repository is unknown, there is no visible upstream for issues or security patches, and the last release was 2018-03-07 with only about 10 stars. That makes it a dormant artifact rather than a maintained dependency. Retrieve the source from Packagist or a forkable mirror and assign clear internal ownership if you proceed.
- Can I use the BotMan Hangouts driver in a standalone PHP project without Laravel?
- Yes, BotMan is framework-agnostic and the overview states the driver works with standalone PHP projects as well as Laravel. You will need to register the driver and route incoming Hangouts webhook events into BotMan yourself. Credentials should be injected through configuration or a secrets manager, not committed to the repository.
- What message features does the Hangouts driver support, such as buttons, cards, and attachments?
- The overview promises the consistent BotMan API for buttons, attachments, and conversations, but a 2018 driver may only support plain text in practice. Hangouts card formats and message shapes have changed since then. Test each feature you need against your target Google Chat surface before relying on it.
- What are alternatives to botman/driver-hangouts for Google Chat bots?
- You can implement the Google Chat API directly behind your own channel adapter, use a maintained BotMan fork, or choose another bot framework that supports Google Chat. The safest pattern is an anti-corruption layer that normalizes inbound events and defines an outbound send interface. That lets you replace the driver without touching conversation logic.
- Is botman/driver-hangouts safe for production use?
- It carries high risk for production because it is dormant, has unknown provenance, and offers no evident security policy or test suite. If you must use it, isolate it behind a thin adapter, store credentials in a secrets manager, add webhook verification, and fork it under an internal namespace with tests. Treat it as a time-boxed spike, not a planning assumption.
Weaver
How can I help you explore Laravel packages today?