meya-ai / community Goto Github PK

Tells user how to interact with the bot

https://developers.facebook.com/docs/messenger-platform/thread-settings/greeting-text

The meya.video component sends to the output webhook API a standard text message with just URL in text.
I think type should be "type": "video" instead of "type": "text".

This lets the component handle the timeout gracefully. Celery does something similar for tasks with timeouts, and it is very useful.

Cards in Meya seem to be missing the forward icon in Facebook that other chatbots show.

Sometimes there are hiccups between Facebook and Meya, and it'd be useful to have those logged to see what's happening. Probably a similar situation with other platforms

Each account (or bot?) should have the ability to include dependencies similar to requirements.txt:

numpy
arrow
urllib3

These package could then be referenced inside components.

King @bye

Structure

1. Getting started
   1. Hello World
   2. List of features
      1. Currently supported
      2. Coming soon
      3. Not supported
2. Core concepts
   1. Flows
   2. Intents
   3. Components
      1. Python
      2. nodejs
      3. dependencies
      4. modules
3. Datastorage (see #1)
   1. Scope
      1. Request
      2. User
      3. Bot
   2. API
      1. set()
      2. get()
      3. update()
      4. put()
      5. delete()
4. Testing
   1. Intents
   2. Flows
   3. Components
   4. Integration
   5. End-to-end
5. WeatherBot Example
   1. Intent
   2. Flow
   3. Component
      1. Request data
      2. API

Components have access to a db object.
Example:

self.db.request.set('name', 'Alice')
print self.db.request.get('name')

https://meya.ai/pizzabot

Useful for reading product feeds, user lists etc

Use-case:

• user invites @meyabot to a Slack channel
• user mentions @meyabot within a channel that should trigger a flow
• @meyabot responds in the channel

Allows up to 10 pre-built responses, useful for navigation

http://messengerblog.com/bots/messenger-platform-1-1-ratings-quick-replies-account-linking-and-more/

Is there a way to connect a bot to multiple FB pages w/ the current messenger integration?

• node.js support
• self.db.user and bot scope
• search(), filter()
• documentation
• bug fixes
• pre-populated user identity: name, username, platform, location (if available)

It would be nice to access things like component time limits via a Python API, rather than defining constants ourselves that we have to keep up to date.

Examples

• meya.input_patter
• meya.input_date
• meya.input_integer
• meya.exists
• meya.set
• meya.pass

Passing "\n" as part of data in component causes an error. Workaround was to break data into smaller pieces, and use new line in meya.text instead.

      Button(text="Share", flow="share", data={'share': share[i]} )

where share[i] = string1 + " \n " + string2

On behalf of @mfts0 "I’ve got a feature request. Turning Intent’s on/off without deleting. "

Solution:

• add "Enabled" check box to feature create/edit view

Added on behalf of @suholet

Use-case:

1. user uploads selfie from Telegram
2. bot parses the uploaded image (as URL)
3. bot forwards the image (as URL) to another bot or email

I looked pretty quickly, but I didn't see any cron job-type support. Are daily messages or questions behavior supported?

I also don't think I have permissions to add the question label...

http://messengerblog.com/bots/messenger-platform-1-1-ratings-quick-replies-account-linking-and-more/

"Most bots have a common “menu” or “settings” option, and we are now making this more consistent and easier to access with the launch of persistent menu. This eliminates the need for people to remember text commands and provides a great way to restart the flow. The menu can be accessed by an icon in the message composer, and will support up to five custom actions."

Use-case:

• Twitter user mentions @meyabot that triggers a flow
• @meyabot responds to the user via DM

Cards should also accept string or pattern input, in addition to buttons, because many people get confused and don't use buttons.

In some cases it's very useful to use a generic component "meya.input_raw" that will store in the output/scope the raw object received from the user.

For example, with FB Messenger platform, using a custom geocoding component, I cannot receive a string (address) or shared location just using meya.input_string.

Meya currently supports Intent integration from the wit.ai platform by integrating your Intent_Name and Accesss_token from wit.ai

Wit.ai recently rolled out some updates to allow for a more intuitive system for working with bots specifically called Bot Engine

As shown here, the old wit.ai console is built around Intents

The new wit.ai console is built around Stories, which are example conversations that you might have with your bot. Intents are completely removed as they were merged with Entities under the Understanding tab in the new console.

The documentation for wit.ai has also been updated to accommodate the new features https://wit.ai/docs/quickstart

Meya.ai should reflect the updated wit.ai console to support Stories and Understanding

Cards should also accept string or pattern input, in addition to buttons, because many people get confused and don't use buttons.

It could be very useful to have a conditional component like the switch/case instruction.

It could me called meya.conditional and it could be very similar to meya.conditional_nlp_intent but based on a custom variable instead of flow.intent.

This could be an example of use

component: meya.conditional
properties:
    scope: flow
    key: mycustomvar
transitions:
    first_value: first_value_state
    second_value: second_value_state
    third_value: third_value_state

The following keyword YAML breaks:

keyword: 1

Temporary workaround:

keyword: '1'

A nice to have.
See [http://atwherebot.com/]

Clients

• Messenger: structured messages (generic, receipt), images
• Live chat: images, buttons, formatted text, links
• Telegram: custom keyboard, images, videos, link, formatted text
• Kik: suggested responses, images, videos, link
• Slack: images, video, links, formatted text

Docs:

• https://developers.facebook.com/docs/messenger-platform/implementation#text_messages
• https://core.telegram.org/bots/api#message
• https://dev.kik.com/#/docs/messaging#message-formats
• https://api.slack.com/docs/formatting

Repro:

• create a "live chat" integration on a bot
• click save
• click "Copy" button on script

It would be nice to have a small storage available for images we might use in the flows instead of having to upload them somewhere else.