This module is intended as a tool to integrate Voiceflow chatbot technology easily and effectively into Drupal projects.
It has been designed to give flexibility in a configurable way, allowing in which routes to add the chatbot, enable or disable it easily, and also integrates if you want to generate an index that uses the Voiceflow tool to know what content you want to be considered by the chatbot or not.
The project is currently in a complete phase, but always with the mentality to scale it and improve or introduce changes that can enrich the functionality and usability of the module, currently it consists of:
- Voiceflow main module, which allows you to configure with the ID provided by the technology easily, also routes where you do not want the chatbot to appear (some provided by default).

- A Voiceflow Index submodule, which allows you to decide, firstly, on which types of content you want to apply that can be indexed, and then for each content, whether you want it to be indexed or not.



As a company, we are installing this module in all our projects where we work with Voiceflow technology.
Project link
| Comment | File | Size | Author |
|---|---|---|---|
| voiceflow_settings.png | 50.88 KB | albeorte | |
| voiceflow_index_settings.png | 93.08 KB | albeorte | |
| voiceflow_index_tab.png | 160.29 KB | albeorte | |
| voiceflow_index.png | 152.4 KB | albeorte |
Comments
Comment #2
albeorte commentedComment #3
vishal.kadamThank you for applying!
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.
The important notes are the following.
phpcs --standard=Drupal,DrupalPracticeon the project, which alone fixes most of what reviewers would report.To the reviewers
Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.
The important notes are the following.
For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.
Comment #4
vishal.kadamRemember to change status, when the project is ready to be reviewed. In this queue, projects are only reviewed when the status is Needs review.
Comment #5
albeorte commentedComment #6
vishal.kadam1. Fix phpcs issues.
2. FILE: voiceflow.module
FILE: modules/voiceflow_index/voiceflow_index.module
The usual description for a .module file is “Hook implementations for the [module name] module”, where [module name] is the module name given in the .info.yml file.
Comment #7
albeorte commentedHello @vishal.kadam,
I have already fix the problems with coding standards.
Thank you very much for your review.
Comment #8
vishal.kadamRest looks fine to me.
Let’s wait for a Code Review Administrator to take a look and if everything goes fine, you will get the role.
Comment #9
avpadernoI will review the project tomorrow.
Comment #10
avpadernoThank you for your contribution and for your patience with the review process!
I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.
These are some recommended readings to help you with maintainership:
You can find more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank the dedicated reviewers as well.
Comment #11
avpaderno