Looking for the best way to deploy Twilio as a SMS send tool within a Filemaker script to notify of order status updates. Nothing too complex. Has anyone successfully achieved this
Twilio is API, try using it with "Insert from URL" and FileMaker Post, although the best way would be using one of the plugins, like free BaseElements, which has curl, proper get and post functions.
Related
wanted to get some additional opinions on a project.
I'm attempting to create a system which will gather the dialog from a call commenced by Twilio Studio and transcribe it. I then intend to push the now transcribed dialog to my CRM.
I found a helpful article on speech to text with the use of Vosk; https://www.twilio.com/blog/transcribe-phone-calls-text-real-time-twilio-vosk - however, I think the article assumes that this will be done with the use of an external application. So, my question is; could this be possibly developed with the use of Twilio Services and leveraged within Studio?
If not, I could develop a web app to connect everything together, but would rather everything be housed within Twilio as I'm a novice developer and developing this app externally sounds like a rather over complex solution to this project.
Thanks in advance for your feedback!
Nothing attempted yet, still in the early research stage of this project.
As of now, Twilio does not offer its own Speech-to-Text engine. However, you can use media streams to forward the audio track to any engine out there on the internet.
This blog post uses Google's engine, for example.
The advantage of such a hosted service is that you neither need to worry about the model nor manage the server. If you want to do 100% serverless, then you could run the entire thing on Twilio Serverless.
In webhooks from Dialogflow, is there a way to trigger Google Assistant APIs, get back the result and display in Dialogflow?
Thanks.
Short answer: no. The Assistant API currently only takes voice input, and there is no way to get the user's voice in Dialogflow. In theory, you could run it through a TTS, feed that to the API, get the response back, and feed that through STT, but that seems like a pain.
What are you actually trying to do?
Google Assistant webhook will not make your bot more intelligent. You need to create right intents in your Dialogflow Agent to make it intelligent enough to do Natural Language Processing and trigger the right intent. Whatever webhook you create (Google Assistant or other) they will just work as you have coded.
In short, Dialogflow is doing the NLP stuff and making your bot intelligent and webhook will do tasks based on the identified intent or action.
To integrate GA with Dialogflow, best way would be to use NodeJS client for Action-on-Google and add it to your webhook project like require('actions-on-google').DialogflowApp
Follow the documentation and understand how to create a GA webhook for Dialogflow.
It would be better if you can explain exactly what you want to do. That way, the community members can answer your question in a better way.
I'm creating an e-mail client for iOS and before the start of working on it, I want to select the best architecture for it.
For example, at the first stage, I want to connect Gmail. I searched and found that Google has a ready library for doing that, so I can just connect the library and fetch my emails.
Another way of doing that is fetching emails from the API in my web server and later to take these emails from my server.
The main purpose is not just to fetch emails, but to be able later to add some new filtrations to it or some other functionalities, maybe machine learning technologies for better personalisation, etc.
Also, I want to support multiple email servers(Gmail, Yahoo, Hotmail, etc.)
What do you advise me to choose, to fetch from my own server or directly from the email servers? I also understand the security issues in the case of using my own servers.
Your feedbacks will help me a lot! Thanks in advance!
You shouldn't use your own server for this task. You just don't need it. It's less secure and I'm pretty sure, that some of your clients will dislike the fact, that you can store their mails on your own server.
If you want to support multiple email server providers, then you should use IMAP protocol for receiving mails and SMTP for sending. Also, in some cases, you can use OAuth2 as authentication method, so you don't need to ask user to enter his credentials in your application.
I recommend you to use some open source libraries for working with IMAP and SMTP, because implementing this protocols by self can be complicated.
Sounds very similar to what I was doing. I was recently building PickedMail where the backend is heavy AI. For Google, you'll want to use Oauth2 and use the server_token to pass in to your server.
I created an iOS framework for this, hope that helps you. https://github.com/Thywis/MultiAccountOauth
For others like outlook, yahoo, iCloud, I'd suggest using IMAP for now.
I am considering using Twillio as an extension in an existing application.
My use-case is this:
User clicks button in application
Using Twilio API, the application calls the user.
The user answers their phone
Twilio connects user to some phone number. (fetched from db)
It's a bit strange, but it is exactly my customer's request. Before I spend too much time in the rabbit hole, I thought I would ask the community, can I do this with Twilio APIs?
Twilio developer here!
This is definitely a common use case for Twilio. In fact, it's so common that we wrote up an in-depth tutorial showing you how to build an app like the one you described.
We've got it in PHP, Node, Python, and Ruby - here's the PHP version:
https://www.twilio.com/docs/howto/walkthrough/click-to-call/php/laravel
If you prefer to just reference the code, you can find it on GitHub too: https://github.com/TwilioDevEd/clicktocall-laravel
Yes. That's actually very simple in Twilio:
https://www.twilio.com/docs/api/rest/making-calls
Can someone explain to me what to consider first when designing a meta-search engine using Erlang, Mnesia and the Yaws web server? This engine should have SMS capability but I am still wondering how I am going to incorporate this feature...
The meta search engine, you need REST or Ajax APIs from Google, Yahoo and Bing. Below am providing you with examples which you may use within your back end HTTP capable Library or your front end JavaScript. I personally use mochiweb and yaws Appmods.
For example: Google has an Ajax search API which works like this:
http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=computers
Hitting that URL will give you a JSON Object which contains several search responses. In this case, the search term is "computers"
Yahoo has what it calls Boss APIs. An example of Yahoo Rest search API using Boss is here below:
For an XML result:
http://boss.yahooapis.com/ysearch/web/v1/animals?appid=APPID&format=xml&start=1&count=3
For a Json result:
http://boss.yahooapis.com/ysearch/web/v1/animals?appid=APPID&format=json&start=1&count=3
Analyse the whole HTTP GET query very well, you notice something they call an APPID. This you will get when you register with them here. I cannot give to you my APPID, you will have to get yours,then paste it in there and you will be good to go. Yahoo has something more powerful called
YQL. In the above query, the search term is: "animals"
Bing as well has got an API for you, but you will need an APPID:
http://api.bing.net/json.aspx?AppId=APPID&Query=love&Sources=Web&Version=2.0&Market=en-us&Web.Count=10
Above, the search term is: "love"
About the Meta Search Engine
You have a web page, people enter search queries in this page. You use your javaScript (JSONP). JSONP could be implemented in any one of your favorite JavaScript Framework you use e.g.
JQUERY,Ext JS,Dojo, Prototype e.t.c
Then you would have to parse the XML or JSON response from the three sources (Google, Yahoo and Bing),and make an appropriate display for your users to navigate the results.
About the SMS part
SMS capability is attained using SMS Gateway. There are several open and close source SMS Gateways. the most powerful of them all is the one built in Erlang/OTP technology called: OSERL, but to test it, you need direct connection with an SMSC in anyone of your local service provider.You need a Port on their SMSC, a user name and a password.There is another one which is better for development reasons called: NowSMS because it has capabilities for USSD, Modem Internet Communication, SMSC service connectivity, HTTP 1.1 and HTTP 1.0, configuration of two-way SMS messaging e.t.c from a Web App to-and -from the SMS Gateway. Go to their site, grab the trial version, follow the documentation and then configure two-way from your web app to the gateway and vice versa. Since NowSMS is not free, you can try: Kannel, it is open source but you will need help from the community to set it up on your Unix or Linux box.
More on incorporating SMS capability in Web Applications can be found:
Here
I also asked once a Question related to development of a powerful search engine using Erlang, Mnesia & YAWS webserver on Stackoverflow. I got plenty of good answers and responses.
Please CLICK ME!
Hope this may help. As I am not sure about SMS thing.