I wanted to use the Gmail smart compose feature in my project. I read many documents but no documents suggest anything related to the implementation of smart compose in Gmail API.
Attaching a link below about the small information about the autocomplete feature:
SmartCompose
Answer:
Unfortunately, this is not possible to do using the Gmail API.
More information:
The Gmail API using the client libraries works on a request-response basis, and these are not retrievable through a Gmail API method. In order to do this, there would need to be a request made each time the string the user is typing changes, which would use not only require a lot of network traffic, but would also make application running slow as many requests would be made.
Feature Request:
On the flip side however, Google already knows about this, and a Feature Request for this has been made on their Issue Tracker. You can view this feature request here, to which you can click the star (☆) in the top left to let Google know more people want this feature to be implemented.
References:
Autocomplete suggestions for text-inputs
Google's Issue Tracker
An API for gmail smart-compose feature
Related
I am doing a proof of concept to find a way to make callouts from Apex code to send automated Whatsapp messages/communications from Salesforce to our customers at difference points of time in Sales life cycle (ex: one at lead conversion, one when a payment is received etc).
My assumption here is to send these messages via triggers. Only thing is i am not able to figure out the correct approach to start with. I did see an example online which is using middleware apps like twilio, weboxapp to convey the messages to Whatsapp servers. Is there a way these communications could be sent directly? Any leads are appreciated!
There appears to be a fairly new integration set up between Salesforce and WhatsApp. There's a good write up in the first link below, and then documentation from Salesforce in the 2nd link. I'd start by looking through there because it might help solve your requirements much more easily. I believe that Whatsapp's APIs are private and need to be accessed through an approved partner.
https://www.wearemarketing.com/blog/salesforce-whatsapp-integration-release.html
https://help.salesforce.com/articleView?id=sf.messaging_set_up_whatsapp.htm&type=5
If any user changes or creates new page in Atlassian Confluence, I would like to automatically send a REST request. I want to use it for pushing auto-messages in messenger (in some public channel). It is useful to see any new changes on wiki.
I found info about REST API for Atlassian Confluence:
https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/
But it is about how to sent requests to Confluence.
Is it possible to generate auto requests from Atlassian Confluence?
Update: I found some information - looks like it is impossible.
https://jira.atlassian.com/browse/CONFSERVER-52487
Am I right?
You are right, unfortunately this functionality does not exist at the moment. The best way would be to write your own Confluence Plugin that binds to certain events. See https://developer.atlassian.com/server/confluence/event-listener-module/ for more information about this. Then you can send the desired requests to your messenger every time the event occurs.
Another option, but unfortunately not free, would be the "Script Runner for Confluence" plugin. This plugin provides at least a simpler way for the above solution. You only have to implement the "send request" part, as the event handling is done by the plugin and can be configured via UI. See http://scriptrunner-docs.connect.adaptavist.com/confluencecloud/script-listeners.html#_set_a_watcher_for_new_blog_posts for more information.
In Mandrill, if you create a new API key and do not limit its API calls, whoever you give that key to can use it to log into the web interface with full access - billing information, account information, the works.
After playing around, it looks like you can disable the web interface login functionality by ticking "Only Allow This Key To Use Certain API Calls" and then selecting at least one API call. Doesn't matter which one.
So I can give full access to the account, or completely disable their ability to log in. Is there any way to customize this further? I would like to be able to limit users to the outbound/inbound UI, or at least prevent them from having the ability to charge many thousands of dollars to the attached credit card. For clarification, my use case is to distribute API keys to contractors or vendors so that all email gets sent through a single account.
I have found very little official Mandrill documentation on this. The only thing that seemed relevant is that if you have a Mailchimp account, you can instead send users there and use the "View Mandrill Reports" functionality. I don't have Mailchimp (nor do I need it), so this seems like an unnecessary hacky workaround.
Different levels of access, other than limiting API calls for API keys isn't currently possible as described in the Mandrill KB here. If someone has access to the web interface, they have access to the account as a whole. This may, of course, change in the future, and would be documented on the blog and in the KB.
I believe you could also restrict access to the web interface by setting up two-factor authentication?
Jeff Lindsay, who coined the term 'webhook', said that the difference between webhook and http callback is that webhooks are user-defined. I think I understand what he meant, but I was thinking about it and I asked myself, can webhooks be effectively used by regular users (I mean: non-developers)?
Usually people don't have a clue how the internet works, they don't know what http is, terms like URL, callback, or request-response don't say anything to them. I've heard that many people do not know the difference between a web browser and a web site, they think that internet really starts at google.com and they type in all urls in the google search box... I mean, what's the use of webhooks when you're not a developer?
Do you think services like AlertGrid make sense? It's a webhook consumer that you can configure to dispatch alerts (SMS, phone, email) either when the callback is NOT received in x amount of time, or when the received data meets user-defined condition, plus it does some data visualization. We wanted it to make webhooks usable for non-developers. But still it requires an initial integration by someone who at least knows how to configure the source to send the webhook events. In many cases it only takes pasting an url to a textbox, but it seems to be beyond the skills of a typical user.
So, are the webhook doomed to be used by software developers only, or is there a chance that millions of Facebook or Twitter users will start making use of them somehow?
I think that something implemented using Webhooks can be made very user friendly.
Suppose Stack Exchange allowed users to define a webhook that would be notified whenever you earned a badge. You could supply a custom URL, or there could be simple buttons to click that would set it up for your Facebook or Twitter account. It could be as simple as the Facebook Like button.
YES I think this is a great idea. It's actually something I designed in my head a couple months ago and didn't think the product existed.
Webhooks are extremely powerful and having a 'service bus' aggregate/manage/dispatch these callbacks is extremely compelling to me.
I think that we are a long way from the general public consuming webhooks in any sort of meaningful way but I don't see why not. I remember when RSS was a 'developer' only technology.
Thanks for the link. I'll be digging in more this weekend.
I am having difficult time in importing contact details from MSN/YAHOO/AOL/GMAIL etc. Can someone tell me how to get the contacts from these networks?
Yahoo Address Book API
Google Contacts API
Windows Live Contacts API
One of the ways is to use the open source library SocialAuth.net
It allows you to get contacts from all the three above, with a very simple API.
CloudSponge.com is a platform that gives you access to these sources and more in a single integration. We use OAuth's 3-legged authentication for services that support it so your users never give their password away. And we have tools to make it easy to integrate; use our widget and get up and running in minutes or use our API and customize every pixel of the user experience.
http://www.cloudsponge.com/developer/