rasa-pro 3.14.0.dev5__py3-none-any.whl → 3.14.0.dev7__py3-none-any.whl

rasa/cli/project_templates/basic/credentials.yml

@@ -1,34 +0,0 @@
-
-# This file contains the credentials for the voice & chat platforms
-# which your bot is using.
-# https://rasa.com/docs/rasa-pro/connectors/messaging-and-voice-channels/
-rest:
-socketio:
-  bot_message_evt: bot_uttered
-  session_persistence: true
-  user_message_evt: user_uttered
-
-rasa:
-  url: "http://localhost:5002/api"
-
-#facebook:
-#  verify: "<verify>"
-#  secret: "<your secret>"
-#  page-access-token: "<your page access token>"
-
-#slack:
-#  slack_token: "<your slack token>"
-#  slack_channel: "<the slack channel>"
-#  slack_signing_secret: "<your slack signing secret>"
-
-#socketio:
-#  user_message_evt: <event name for user message>
-#  bot_message_evt: <event name for bot messages>
-#  session_persistence: <true/false>
-
-#mattermost:
-#  url: "https://<mattermost instance>/api/v4"
-#  token: "<bot token>"
-#  webhook_url: "<callback URL>"
-
-

rasa/cli/project_templates/basic/data/general/feedback.yml

@@ -1,20 +0,0 @@
-# Simple thumbs up/down feedback flow
-flows:
-  leave_feedback:
-    description: This flow collects simple thumbs up or thumbs down feedback
-    if: False # Flow guard to prevent direct triggering
-    steps:
-      - collect: feedback_rating
-        description: Ask user for thumbs up or thumbs down feedback
-      - id: feedback_response
-        noop: true
-        next:
-          - if: slots.feedback_rating == "thumbs_up"
-            then: positive_response
-          - else: negative_response
-      - id: positive_response
-        action: utter_thankyou_positive
-        next: END
-      - id: negative_response
-        action: utter_thankyou_negative
-        next: END

rasa/cli/project_templates/basic/data/general/goodbye.yml

@@ -1,6 +0,0 @@
-flows: 
-  goodbye_flow:
-    description: Handle user goodbye messages, say farewell, and collect feedback
-    steps:
-      - action: utter_goodbye
-      - link: leave_feedback

rasa/cli/project_templates/basic/data/general/hello.yml

@@ -1,7 +0,0 @@
-flows:
-  hello:
-    description: Flow for greeting the user hello
-    name: hello
-    steps:
-      - action: utter_greeting
-

rasa/cli/project_templates/basic/data/general/help.yml

@@ -1,6 +0,0 @@
-flows:
-  help:
-    description: Answer the users question on what the assistant can do to help them
-    name: help
-    steps:
-      - action: utter_help

rasa/cli/project_templates/basic/data/general/human_handoff.yml

@@ -1,16 +0,0 @@
-version: "3.1"
-flows:
-  human_handoff:
-    description: Handles escalation to a live human agent.
-    steps:
-      - collect: confirm_human_handoff
-        ask_before_filling: True
-        next:
-          - if: slots.confirm_human_handoff is "Yes"
-            then:
-              - action: utter_transferring_to_human
-              - action: action_human_handoff
-                next: END
-          - else:
-              - action: utter_human_handoff_cancelled
-                next: END

rasa/cli/project_templates/basic/data/general/welcome.yml

@@ -1,9 +0,0 @@
-flows:
-  welcome:
-    if: False
-    description: |
-      This flow is designed to greet and onboard new users who initiate a welcome intent.
-      It begins with an initial greeting message to establish a friendly interaction.
-    name: say hello
-    steps:
-      - action: utter_greeting

rasa/cli/project_templates/basic/data/system/pattern_completed.yml

@@ -1,7 +0,0 @@
-flows: 
-  pattern_completed:
-    description: A flow has been completed and there is nothing else to be done
-    if: False
-    steps:
-      - noop: true
-        next: END

rasa/cli/project_templates/basic/data/system/pattern_correction.yml

@@ -1,7 +0,0 @@
-flows:
-  pattern_correction:
-    description: Handle a correction of a slot value.
-    name: pattern correction
-    steps:
-      - action: action_correct_flow_slot
-        next: "END"

rasa/cli/project_templates/basic/data/system/pattern_search.yml

@@ -1,8 +0,0 @@
-flows:
-  pattern_search:
-    name: pattern_search
-    description: Flow for handling knowledge-based questions
-    steps:
-    - id: 0_action_trigger_search
-      next: END
-      action: action_trigger_search

rasa/cli/project_templates/basic/data/system/pattern_session_start.yml

@@ -1,8 +0,0 @@
-flows:
-  pattern_session_start:
-    description: Flow for starting the conversation
-    name: pattern session start
-    nlu_trigger:
-        - intent: session_start
-    steps:
-      - link: hello

rasa/cli/project_templates/basic/docs/rasa_assistant_qa.txt

@@ -1,65 +0,0 @@
-1. Rasa Assistant Capabilities
-
-Q: What is a Rasa assistant?
-A: A Rasa assistant is an AI-powered conversational bot built using the Rasa framework. It can understand natural language, manage complex conversations, execute actions, and integrate with external systems to help users accomplish tasks through text or voice interactions.
-
-Q: What types of tasks can Rasa assistants handle?
-A: Rasa assistants can handle a wide variety of tasks including customer support, booking appointments, processing transactions, answering FAQs, collecting information through forms, routing calls to human agents, providing personalized recommendations, and integrating with databases and APIs.
-
-Q: How does a Rasa assistant understand what users say?
-A: Rasa assistants use Natural Language Understanding (NLU) to interpret user messages. They can extract intents (what the user wants to do) and entities (important information like names, dates, amounts) from text. Rasa Pro also supports LLM-based understanding for more flexible conversation handling.
-
-2. Conversation Management
-
-Q: Can Rasa assistants handle complex conversations?
-A: Yes, Rasa assistants excel at managing complex, multi-turn conversations. They use dialogue management to track conversation context, remember previous interactions, and guide users through multi-step processes like filling out forms or completing transactions.
-
-Q: What are Rasa flows?
-A: Rasa flows are a powerful feature that allows you to define conversational workflows with branching logic, conditional steps, and data collection. They make it easy to create structured conversations for tasks like onboarding, troubleshooting, or gathering customer information.
-
-Q: Can the assistant handle interruptions and context switching?
-A: Absolutely! Rasa assistants can handle conversation repairs, interruptions, clarifications, and context switching. Users can change topics mid-conversation or ask for help, and the assistant will respond appropriately while maintaining conversation state.
-
-3. Integration and Actions
-
-Q: Can Rasa assistants connect to external systems?
-A: Yes, Rasa assistants can integrate with virtually any external system through custom actions. They can connect to databases, APIs, CRM systems, payment processors, booking systems, and more to perform real-world tasks on behalf of users.
-
-Q: What are custom actions in Rasa?
-A: Custom actions are Python functions that allow your assistant to perform specific tasks like querying databases, calling APIs, processing payments, sending emails, or any other business logic. They bridge the gap between conversation and real-world actions.
-
-Q: Can Rasa assistants work with existing business systems?
-A: Yes, Rasa assistants are designed to integrate seamlessly with existing business infrastructure. They can connect to your CRM, ERP, databases, microservices, and other enterprise systems through APIs and custom integrations.
-
-4. Advanced Features
-
-Q: Does Rasa support voice interactions?
-A: Yes, Rasa assistants can handle voice interactions through integration with speech-to-text and text-to-speech services. They can be deployed as voice bots for phone systems or voice-enabled applications.
-
-Q: Can Rasa assistants learn and improve over time?
-A: Rasa assistants can be continuously improved through conversation analytics, user feedback, and retraining with new data. Rasa X (now part of Rasa Pro) provides tools for reviewing conversations and improving assistant performance.
-
-Q: What is CALM in Rasa?
-A: CALM (Conversational AI with Language Models) is Rasa's architecture that combines traditional rule-based dialogue management with large language models. This provides both reliability and flexibility, allowing for structured workflows while handling unexpected user inputs gracefully.
-
-5. Deployment and Scaling
-
-Q: Where can Rasa assistants be deployed?
-A: Rasa assistants can be deployed anywhere - on websites as chatbots, in mobile apps, on messaging platforms (WhatsApp, Slack, Facebook Messenger), as voice bots, in call centers, or as standalone applications. They're platform-agnostic and highly flexible.
-
-Q: Can Rasa assistants handle multiple languages?
-A: Yes, Rasa supports multilingual assistants. You can train models in different languages and create assistants that can communicate with users in their preferred language.
-
-Q: How do Rasa assistants scale for enterprise use?
-A: Rasa assistants are built for enterprise scale with features like clustering, load balancing, conversation analytics, version control for models, A/B testing capabilities, and enterprise-grade security and compliance features.
-
-6. Use Cases and Industries
-
-Q: What industries use Rasa assistants?
-A: Rasa assistants are used across many industries including banking and finance, healthcare, e-commerce, telecommunications, insurance, travel and hospitality, education, and government services. Any industry that needs to automate customer interactions can benefit.
-
-Q: Can Rasa assistants replace human agents?
-A: Rasa assistants are designed to augment human agents, not replace them. They can handle routine inquiries and tasks, freeing up human agents for complex issues that require empathy, creativity, or specialized knowledge. They can also seamlessly hand off conversations to humans when needed.
-
-Q: What's the difference between Rasa and simple chatbots?
-A: Unlike simple rule-based chatbots, Rasa assistants can understand context, handle complex multi-turn conversations, learn from interactions, integrate with business systems, and manage sophisticated workflows. They're true conversational AI rather than basic question-answering systems. 

rasa/cli/project_templates/basic/docs/template.txt

@@ -1,7 +0,0 @@
-1. General Questions
-
-Q: What else can you do?
-A: I can answer questions from docs. Add more txt files to /docs to get started. 
-
-Q: Can you do RAG?
-A: Yes, you can use Retrieval-Augmented Generation (RAG) with Rasa. Rasa's CALM architecture supports RAG through its Enterprise Search Policy. Right now, I'm just retrieving messages from the /docs folder for demo purposes. Add more txt files to /docs to test it out.

rasa/cli/project_templates/basic/domain/general/assistant_details.yml

@@ -1,12 +0,0 @@
-slots:
-  skills_summary:
-    type: text
-    initial_value: "general questions or direct you to an available agent"
-    mappings:
-      - type: controlled
-  assistant_name:
-    type: text
-    initial_value: "Vanessa"
-    mappings:
-      - type: controlled
-

rasa/cli/project_templates/basic/domain/general/bot_identity.yml

@@ -1,5 +0,0 @@
-responses:
-  utter_bot_identity:
-    - text: "Yes, I'm an AI assistant designed to help you with your questions. I'm here to provide helpful information and support. How can I assist you today?"
-    - text: "I am indeed an AI assistant! I'm programmed to be helpful, accurate, and friendly. What can I help you with?"
-    - text: "That's right, I'm an AI bot created to assist you. I aim to provide useful responses and help solve your questions. Is there something specific I can help you with?"

rasa/cli/project_templates/basic/domain/general/cannot_handle.yml

@@ -1,5 +0,0 @@
-responses:
-  utter_no_relevant_answer_found:
-    - text: I’m sorry, I can’t help with that.
-      metadata:
-        rephrase: False

rasa/cli/project_templates/basic/domain/general/feedback.yml

@@ -1,28 +0,0 @@
-slots:
-  feedback_rating:
-    type: categorical
-    values: [thumbs_up, thumbs_down]
-    mappings:
-      - type: from_llm
-
-responses:
-  utter_ask_feedback_rating:
-    - text: "Before you go, how was your experience?"
-      buttons:
-        - title: "👍 Great"
-          payload: "/SetSlots(feedback_rating=thumbs_up)"
-        - title: "👎 Could be better"
-          payload: "/SetSlots(feedback_rating=thumbs_down)"
-
-  utter_thankyou_positive:
-    - text: "That's wonderful to hear! Thank you for your feedback! Have a fantastic day! 🌟"
-    - text: "So glad we could help! Thanks for the positive feedback! Take care! 😊"
-    - text: "Amazing! We're thrilled you had a great experience. Have a wonderful day! 🎉"
-
-  utter_thankyou_negative:
-    - text: "Thank you for your honest feedback. We're always working to improve our service. Have a good day."
-    - text: "We appreciate your feedback and will use it to make our service better. Thank you for your time."
-    - text: "Thanks for letting us know. Your feedback helps us improve. Take care!"
-
-actions:
-  - action_default_fallback

rasa/cli/project_templates/basic/domain/general/goodbye.yml

@@ -1,7 +0,0 @@
-responses: 
-  utter_goodbye:
-    - text: "Thanks for stopping by — take care!"
-    - text: "Thanks for the chat. Have a great day!"
-    - text: "Catch you later! Feel free to reach out anytime."
-    - text: "Goodbye for now — we’re here if you need anything."
-    - text: "Take care! Let us know if you have any other questions."

rasa/cli/project_templates/basic/domain/general/help.yml

@@ -1,5 +0,0 @@
-version: "3.1"
-
-responses:
-  utter_help:
-    - text: "I can help you with {skills_summary}."

rasa/cli/project_templates/basic/domain/general/human_handoff_domain.yml

@@ -1,35 +0,0 @@
-version: "3.1"
-actions:
-  - "action_human_handoff"
-
-intents:
-  - human_handoff
-  - speak_to_agent
-  - talk_to_human
-  - escalate
-
-slots: 
- confirm_human_handoff:
-    type: "categorical"
-    mappings:
-      - type: "from_llm"
-    values:
-      - "Yes"
-      - "No" 
-
-responses:
-  utter_ask_confirm_human_handoff:
-    - text: "Do you want to be connected to a human agent?"
-      buttons:
-        - payload: "/SetSlots(confirm_human_handoff=Yes)"
-          title: "Yes"
-        - payload: "/SetSlots(confirm_human_handoff=No)"
-          title: "No"
-
-  utter_transferring_to_human:
-    - text: "You will be transfered to a human agent in a few moments."
-
-  utter_human_handoff_cancelled:
-    - text: "Ok, I understand you don't want to be connected to a human agent. Is there something else I can help you with?"
-      metadata:
-        rephrase: True

rasa/cli/project_templates/basic/domain/general/utils.yml

@@ -1,13 +0,0 @@
-version: "3.1"
-
-slots:
-  current_date:
-    type: text
-  username:
-    type: text
-  email_address:
-    type: text
-  physical_address:
-    type: text
-  segment:
-    type: text

rasa/cli/project_templates/basic/domain/general/welcome.yml

@@ -1,7 +0,0 @@
-version: "3.1"
-
-responses:
-  utter_greeting:
-    - text: "Hi there! I'm {assistant_name}. I can help you with {skills_summary}. How can I help you today?"
-      metadata:
-        rephrase: True

rasa/cli/project_templates/basic/endpoints.yml

@@ -1,73 +0,0 @@
- # This file contains the different endpoints your bot can use.
-
-# Server which runs your custom actions.
-# https://rasa.com/docs/rasa-pro/concepts/custom-actions
-action_endpoint:
-  actions_module: "actions"
-
-# Allow rephrasing of responses using a Rasa-hosted model
-nlg:
-  type: rephrase
-  llm:
-    model_group: openai-gpt-4o
-  prompt_template: ./prompts/rephraser_demo_personality_prompt.jinja2
-  rephrase_all: False
-  summarize_history: False
-
-# Model Groups - Integrate with different LLM providers
-# https://rasa.com/docs/reference/config/components/llm-configuration/#model-groups
-# https://platform.openai.com/docs/models
-model_groups:
-  - id: openai-gpt-4o
-    models:
-      - provider: openai
-        model: gpt-4o-2024-11-20
-        timeout: 7
-        temperature: 0.0
-        top_p: 0.0
-  - id: gpt-3.5-turbo-openai-model
-    models:
-      - provider: openai
-        model: gpt-3.5-turbo
-        temperature: 0.3
-  # - id: rasa_command_generation_model
-  #   models:
-  #     - provider: rasa
-  #       model: rasa/cmd_gen_codellama_13b_calm_demo
-  #       api_base: "https://tutorial-llm.rasa.ai"
-  # - id: openai_embeddings
-  #   models:
-  #     - provider: openai
-  #       model: text-embedding-ada-002
-
-
-# Server where the models are pulled from.
-# https://rasa.com/docs/rasa-pro/production/model-storage#fetching-models-from-a-server
-#models:
-#  url: http://my-server.com/models/default_core@latest
-#  wait_time_between_pulls:  10   # [optional](default: 100)
-
-# Tracker store which is used to store the conversations.
-# By default the conversations are stored in memory.
-# https://rasa.com/docs/rasa-pro/production/tracker-stores
-#tracker_store:
-#    type: redis
-#    url: <host of the redis instance, e.g. localhost>
-#    port: <port of your redis instance, usually 6379>
-#    db: <number of your database within redis, e.g. 0>
-#    password: <password used for authentication>
-#    use_ssl: <whether or not the communication is encrypted, default false>
-#tracker_store:
-#    type: mongod
-#    url: <url to your mongo instance, e.g. mongodb://localhost:27017>
-#    db: <name of the db within your mongo instance, e.g. rasa>
-#    username: <username used for authentication>
-#    password: <password used for authentication>
-
-# Event broker which all conversation events should be streamed to.
-# https://rasa.com/docs/rasa-pro/production/event-brokers
-#event_broker:
-#  url: localhost
-#  username: username
-#  password: password
-#  queue: queue

rasa/cli/project_templates/basic/prompts/rephraser_demo_personality_prompt.jinja2

@@ -1,19 +0,0 @@
-The following is a conversation with an AI assistant.
-The assistant is professional, calm, and highly attentive to detail.
-Its main priorities are efficiency, speed, and accuracy when handling user requests.
-
-Please rephrase the suggested AI response, staying close to the original meaning while
-ensuring the assistant's tone remains formal yet empathetic, friendly, and reassuring.
-It should convey patience, even with vague or repetitive questions, and be clear,
-informative, and slightly humorous where appropriate.
-
-Write your responses in English
-
-Context / previous conversation with the user:
-{{history}}
-
-{{current_input}}
-
-Suggested AI Response: {{suggested_response}}
-
-Rephrased AI Response:

rasa/cli/project_templates/finance/actions/__init__.py

@@ -1,46 +0,0 @@
-# Account actions
-from actions.accounts.action_ask_account import ActionAskAccount
-from actions.accounts.action_check_balance import ActionCheckBalance
-
-# General actions
-from actions.action_session_start import ActionSessionStart
-
-# Card actions
-from actions.cards.action_ask_card import ActionAskCard
-from actions.cards.action_check_card_existence import ActionCheckCardExistence
-from actions.cards.action_update_card_status import ActionUpdateCardStatus
-
-# Transfer actions
-from actions.transfers.action_add_payee import ActionAddPayee
-from actions.transfers.action_ask_account_from import ActionAskAccountFrom
-from actions.transfers.action_check_payee_existence import ActionCheckPayeeExistence
-from actions.transfers.action_check_sufficient_funds import ActionCheckSufficientFunds
-from actions.transfers.action_list_payees import ActionListPayees
-from actions.transfers.action_process_immediate_payment import (
-    ActionProcessImmediatePayment,
-)
-from actions.transfers.action_remove_payee import ActionRemovePayee
-from actions.transfers.action_schedule_payment import ActionSchedulePayment
-from actions.transfers.action_validate_payment_date import ActionValidatePaymentDate
-
-__all__ = [
-    # General actions
-    "ActionSessionStart",
-    # Account actions
-    "ActionAskAccount",
-    "ActionCheckBalance",
-    # Card actions
-    "ActionAskCard",
-    "ActionCheckCardExistence",
-    "ActionUpdateCardStatus",
-    # Transfer actions
-    "ActionAddPayee",
-    "ActionAskAccountFrom",
-    "ActionCheckPayeeExistence",
-    "ActionCheckSufficientFunds",
-    "ActionListPayees",
-    "ActionProcessImmediatePayment",
-    "ActionRemovePayee",
-    "ActionSchedulePayment",
-    "ActionValidatePaymentDate",
-]

rasa/cli/project_templates/finance/actions/accounts/action_ask_account.py

@@ -1,47 +0,0 @@
-from typing import Any, Dict, List, Text
-
-from rasa_sdk import Action, Tracker
-from rasa_sdk.executor import CollectingDispatcher
-
-from actions.database import Database
-
-
-class ActionAskAccount(Action):
-    def name(self) -> Text:
-        return "action_ask_account"
-
-    def run(
-        self,
-        dispatcher: CollectingDispatcher,
-        tracker: Tracker,
-        domain: Dict[Text, Any],
-    ) -> List[Dict[Text, Any]]:
-        name = tracker.get_slot("name")
-
-        db = Database()
-
-        # Get user information
-        user = db.get_user_by_name(name)
-        if not user:
-            dispatcher.utter_message(text="User not found.")
-            return []
-
-        # Get all accounts for the user
-        user_id = int(user["id"])
-        accounts = db.get_accounts_by_user(user_id)
-
-        if not accounts:
-            dispatcher.utter_message(text="No accounts found for this user.")
-            return []
-
-        buttons = [
-            {
-                "title": f"{account['number']} ({account['type'].title()})",
-                "payload": account["number"],
-            }
-            for account in accounts
-        ]
-        message = "Which account would you like the balance for?"
-        dispatcher.utter_message(text=message, buttons=buttons)
-
-        return []

rasa/cli/project_templates/finance/actions/accounts/action_check_balance.py

@@ -1,40 +0,0 @@
-from typing import Any, Dict, List, Text
-
-from rasa_sdk import Action, Tracker
-from rasa_sdk.executor import CollectingDispatcher
-
-from actions.database import Database
-
-
-class ActionCheckBalance(Action):
-    def name(self) -> Text:
-        return "action_check_balance"
-
-    def run(
-        self,
-        dispatcher: CollectingDispatcher,
-        tracker: Tracker,
-        domain: Dict[Text, Any],
-    ) -> List[Dict[Text, Any]]:
-        name = tracker.get_slot("name")
-        account_number = tracker.get_slot("account")
-
-        db = Database()
-
-        # Get user information
-        user = db.get_user_by_name(name)
-        if not user:
-            dispatcher.utter_message(text="User not found.")
-            return []
-
-        # Get account information
-        account = db.get_account_by_user_and_number(int(user["id"]), account_number)
-        if not account:
-            dispatcher.utter_message(text="Account not found.")
-            return []
-
-        current_balance = float(account["balance"])
-
-        message = f"The balance on that account is: ${current_balance}"
-        dispatcher.utter_message(text=message)
-        return []

rasa/cli/project_templates/finance/actions/action_session_start.py

@@ -1,74 +0,0 @@
-from datetime import datetime
-from typing import Any, Dict, List, Text
-
-from rasa_sdk import Action, Tracker
-from rasa_sdk.events import ActionExecuted, SlotSet
-from rasa_sdk.executor import CollectingDispatcher
-
-from actions.database import Database
-
-
-class ActionSessionStart(Action):
-    def name(self) -> Text:
-        return "action_session_start"
-
-    def set_current_date(self) -> List[Dict[Text, Any]]:
-        current_date = datetime.now().strftime("%d/%m/%Y")
-        return [SlotSet("current_date", current_date)]
-
-    def set_user_profile(self, name: str) -> List[Dict[Text, Any]]:
-        db = Database()
-
-        # Get user information
-        user = db.get_user_by_name(name)
-
-        if user:
-            return [
-                SlotSet("name", user["name"]),
-                SlotSet("username", user["username"]),
-                SlotSet("segment", user["segment"]),
-                SlotSet("email_address", user["email"]),
-                SlotSet("physical_address", user["address"]),
-            ]
-        else:
-            return []
-
-    def run(
-        self,
-        dispatcher: CollectingDispatcher,
-        tracker: Tracker,
-        domain: Dict[Text, Any],
-    ) -> List[Dict[Text, Any]]:
-        current_date_events = self.set_current_date()
-
-        # Advanced option: It is possible to enable the chatbot with multiple
-        # user profiles.
-        # This option influences the interactions with the assistant.
-        # The bot randomly assigns a user profile at the start of each session.
-        # With this advance option: The demo bot will include three user profiles
-        # with different payees:
-        # John Smith: Payees: Robert (friend), James (son), Food Market (groceries)
-        # Mary Brown: Payees: Richard (business partner), Susan (friend),
-        # Electric Company (utilities)
-        # Dan Young: Payees: Amy (colleague), Fitness Gym (gym), William (friend)
-        #
-        # The default profile is John Smith
-        #
-        # Each profile also has its own accounts—Current (Checking), Savings,
-        # and Business
-        #
-        # Intructions: Just toggle the comments of the following 2 lines.
-        name = "John Smith"
-        # username = random.choice(["John Smith", "Mary Brown", "Dan Young"])
-
-        user_profile_events = self.set_user_profile(name)
-
-        events = (
-            current_date_events
-            + user_profile_events
-            + [
-                ActionExecuted("action_listen"),
-            ]
-        )
-
-        return events