I'd like to ask users for their name and email when they open the Smooch web widget, before the chat can be started. Similar to what Frank & Oak does: https://global.frankandoak.com/
I'm not very technical but can find my way around some HTML, CSS and even some javascript. I was hoping someone at Smooch would see my post and provide me with guidance on how to implement this :)
I'd need the name and email to be sent to Front (which I'm using to handle Smooch messages).
I know this might be a lot to ask, but if you find the time to help me, you can then add the answer to your documentation, which would be really cool for non-technical users like me.
Cheers!
From Smooch Web Messenger FAQ
How can I capture user’s info before starting the conversation with the user on the web?
You can create a form on your website and pass us the info in Smooch.init().
Related
I have a use scenario where I'm testing a bot in google hangout. To facilitate testing of multiple users, I'd like to create a series of other bots that replicate the functions of users. But this is all dependent on the bots in the room listening to one another. It also requires that I get the userid of the bots so they can name each other. In Google Scripts I can find no way to retrieve that (the rest API is not an option).
Any suggestions?
The information is documented, but I understand GCP docs aren't the easiest to navigate. According to the Event Format reference: "Only messages from "real", non-bot users are delivered to bots. A bot will never receive messages posted by itself or by a different bot."
So the answer to the question appears to be no. Bots do not appear to be able to talk to each other. When you put the userid in the text property of the bot it does not replace it to an #botname as it does with human users. If anyone can figure out another way to do it I would appreciate it.
But the second question of where to get the bots userid I can now answer and I leave here in case anyone else is curious. This appears only in a message event, when a bot is mentioned as the property event.message.annotations[0].userMention.user.name
At the beginning, I want to apologize for non-developer question. I wasn't able ask this on Meta, because Meta requires 5 reputation just to be able ask any questions.
Question: We want to integrate Spotify for commercial project for Android and iOS users to make them able use music through Spotify.
So where we can get Spotify's approval? How we can sign a contract to start cooperation?
We asked this on Facebook in Spotify official page, they sent us here to ask these.
On the Spotify's website, no email to contact for.
With respect,
Rus
Operation department
Arielle from Spotify here.
If you create a application in the Dashboard on Spotify for Developers (https://beta.developer.spotify.com/dashboard/), you will be prompted to go through a commercial request form, which will ask you for more information about your app. The appropriate teams can then follow up about your request.
I am not able to create any openshift apps .
I currently have only one app main-anandu.rhcloud.com which points to anandu.info .
but when i create an app it says "i have reached gear limit of 0"?
I tried to ask on IRC but it failed
Its mostly because your application violated our legal terms. We understand that this isn't always intentional. So the best thing for your to do is first check your email inbox (the one that's associated with your account) for an email from us explaining why your application was removed. If you still have questions or can't find the email please feel free to email us at Openshift#redhat.com with your login ID and url of your app and I'll look into it.
Is it possible to get the friends "email address" using graph api ?
I am not totally sure, but as a measure of spam prevention I don't think Facebook makes this accessible without the permission of your friend.
Yes, have them authorize your app. Otherwise, nope not possible. Make it so your app is so cool and entertaining that they cannot resist giving up such personal information as their email to partake of your app.
yes and no. If you take a friend's "username" and append #facebook.com, you have an email address that you can use to send a message. However, this message will not arrive as an ordinary facebook message in the receivers "Inbox", but it will be sorted into the "Other" Messaging folder.
I am an android application developer (trying to be one) and I want to learn how to communicate with web sites from my applications. However, I don't know where to start. Can you point me in the right direction?
PS : I believe "web communcation standarts" is wrong term but i don't know how to call them.
I'd suggest that you learn by doing. Pick an idea - let's say you want to upload a picture from your Android phone to facebook.
Now go and research how to do that. Facebook exposes what they call the "Graph API" for all fb resources, including users, statuses, and photos, among other things. The Graph API is a REST API - in other words each item on the backend is modelled as a "resource" which is accessible from a URL. (Learn more about REST on wikipedia). Send a GET HTTP message to the given URL and you can get information on the resource. Send a POST to the container of that resource, and you can add another of whatever it is. In this model, to add a photo, you POST to the album URL. Read on FB for how to do that. They call it "publishing".
But reading that doc page you learn that in order to POST you need an authorization token.
Your app needs publish_stream permissions. How do you get that? Keep reading in the FB doc and you'll see a link to the Authentication and authorization guide. That tells you about how to use OAuth 2.0 in Facebook apps.
Your app will send its first feeble message out, and get an error response. Why? You'll want to examine the message. so you google and figure out that you can use an http debugging proxy to help you, something like Fiddler2 for Windows, or Charles for other systems. So you download that, set the proxy on your Android device, and now you can view outgoing HTTP messages and their responses on your PC.
Keep plugging along, learning what you need to accomplish the task in front of you: in this example, posting a photo from an android device to Facebook.
After you reach that goal, you will have learned quite a bit of practical knowledge for this domain of problem. Then you can try a new goal, and work on that.
After a few iterations of this, you will have learned how to learn, which is even better than learning REST or OAuth. If you know how to learn, the sky's the limnit.
Learn about HTTP first. There is far more to HTTP than there first appears. It is a building block for everything on the web.
You will not go wrong by getting very familiar with this http://www.w3.org/Protocols/rfc2616/rfc2616.html