Page MenuHomePhabricator
Create Task
Maniphest T6405

Support for Gmail Inbox actions
Closed, WontfixPublic
Actions

Description

For implementation:
https://developers.google.com/gmail/markup/reference/go-to-action

Original Ticket

There is such nice thing as Gmail Inbox Actions: https://developers.google.com/gmail/actions/ , that allow to put custom links next to the message in inbox in Gmail. These links for example can be used to view associated commit, issue or anything else which caused e-mail to be sent.

See how GitHub has used these: https://github.com/blog/1891-view-issue-pull-request-buttons-for-gmail

It would be great to have support for them in Phabricator as well.

Related Objects

Event Timeline

aik099 created this task.Oct 28 2014, 8:29 AM
aik099 raised the priority of this task from to Needs Triage.
aik099 updated the task description. (Show Details)
aik099 added projects: Notifications, Audit.
aik099 added a subscriber: aik099.
epriestley triaged this task as Wishlist priority.Oct 28 2014, 11:21 AM
epriestley added a subscriber: epriestley.
chad removed a project: Audit.Oct 29 2014, 4:32 AM
avivey merged a task: T6493: Implement gmail action markup for mail notifications.Nov 7 2014, 6:43 PM
avivey added a subscriber: champo.
chad claimed this task.Nov 7 2014, 6:44 PM
chad added a project: Mail.
jsotuyod added a subscriber: jsotuyod.Nov 7 2014, 6:46 PM
avivey added a subscriber: avivey.Nov 7 2014, 6:48 PM

Note that there's a non-trivial per-install cost here (White-listing the application x domain with Google).

chad added a comment.Nov 7 2014, 7:13 PM

Where did you run into that? I haven't seen it in the docs, offhand.

chad updated the task description. (Show Details)Nov 7 2014, 7:13 PM
avivey added a comment.Nov 7 2014, 7:17 PM

https://developers.google.com/gmail/markup/registering-with-google

I've looked at it when it first came out, so maybe it was streamlined a bit since.

Instructions say "Fill out the registration form and we will get back to you," and the form looks like it's being handled by humans: https://docs.google.com/forms/d/1PA-vjjk3yJF7MLPOVKbIz3MBfhyma2obS8NIZ0JYx8I/viewform?pli=1

chad added a comment.Nov 7 2014, 7:37 PM

Interesting, understandable. I'm curious though why your own domain (sending/receiving) isn't automatically whitelisted.

chad removed chad as the assignee of this task.EditedNov 7 2014, 7:37 PM
chad added a project: Phacility.
chad added a subscriber: chad.

Will revisit with Phacility down the road. Even if we implemented, it seems unlikely users would be able to use it on local installs.

btrahan moved this task from Backlog to Do After Launch on the Phacility board.Nov 11 2014, 10:39 PM
chad added a project: User Delight.Nov 11 2014, 10:58 PM
chad removed a project: Notifications.
btrahan merged a task: T6587: Implement Schema.org call for action markup to emails.Nov 19 2014, 2:38 AM
btrahan added a subscriber: dereckson.
btrahan added a subscriber: btrahan.
btrahan removed a subscriber: btrahan.
dereckson added a comment.Nov 19 2014, 2:55 AM
In T6405#82741, @chad wrote:

Even if we implemented, it seems unlikely users would be able to use it on local installs.

The Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least. criteria seems complicated to met for small teams, but reachable for larger installs.

The DKIM and SPF conditions are easily met using services like Mandrilapp (DKIM DNS records are mandrill._domainkey.<sending domain>), so that doesn't require clever SMTP tweaking.

Now, I dont know how to interpret We are currently only approving Go-To actions for very specific high-value usecase with high interaction rate (e.g. Flight Check-in, Shipment tracking links)..

epriestley moved this task from Do After Launch to Do Eventually on the Phacility board.Jan 20 2015, 10:03 PM
chad removed a project: User Delight.Apr 14 2015, 7:02 PM
eadler added a subscriber: eadler.Apr 29 2015, 11:06 PM
ox added a subscriber: ox.Jun 9 2015, 3:17 PM
eadler added a project: Restricted Project.Feb 18 2016, 6:50 PM
eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
tony612 added a subscriber: tony612.Apr 18 2016, 4:08 PM
Arcank added a subscriber: Arcank.Jun 3 2016, 9:36 PM

More doc on a different way to markup the email:
https://developers.google.com/gmail/markup/reference/formats/json-ld

chad added a comment.Jun 3 2016, 11:26 PM

Afaik you still have to be white listed. Has that changed?

chad added a comment.Jun 3 2016, 11:59 PM

Also:

Emails must come from a static email address, e.g. foo@bar.com

Actually, that probably means this task is no-op.

eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jul 4 2016, 9:16 PM
epriestley closed this task as Wontfix.Jul 16 2016, 2:20 PM
epriestley claimed this task.

We don't send from a static address, even in Phacility, since each install sends mail that originates from an install-specific address (@phabricator.mycompany.com or @instance.phacility.com). This is currently a hard requirement for these actions.

If you're interested in this, ask Google to provide a way for us to support it. As an organization, we don't have the resources to undertake speculative business development projects like this, nor any belief that we can convince Google to change its behavior for us. If we did have this kind of relationship capital with Google we'd spend it on supporting Gmail header filtering long before action buttons.

Otherwise, we'll look at this again once we acquire Google.

(We've recently added a similar button to the body of the mail in Differential, and I expect to add this button to other applications in the future. This isn't as easy to get at as a subject line action would be, but it may make it slightly easier to follow links from mail.)

Phabricator · Built by Phacility