How to add invitees to events using Salesforce1 mobile app


Since quick actions support lightning components now, I released a lightning component version with renewed lookup component here — I would recommend using this component instead

Out of the box, Salesforce1 provides an ‘Events’ app that allows you to view your events and check the attendees. However, it doesn’t allow you add additional invitees, which could come in very handy if you are on the road and have to quickly invite additional contacts, leads or users. This requirement has come up a couple of times when I talk about mobile use cases with customers. There is also an idea out there in idea exchange —

Agreed, this would be a nice feature to have but currently I am not sure if this is something that is being considered in the roadmap for Salesforce1 app. So, I built a custom Visualforce page that you can use to add additional invitees to your events using the mobile app.

Follow the steps below to implement this in your org. And ofcouse, please do test this in Sandbox before you use it in production

  1. Download the code and resources from this unmanaged package — Rename the components to suit your naming convention, if required.
  2. Then in Setup->Build->Customize->Activities->Event Buttons and Links->New Action, create a new quick action called ‘Add Invitees’ (or call it whatever you want). Change the icon as you see fit.
  3. Choose the action type as ‘Custom Visualforce page’ and choose the Visualforce page as ‘ZKKS1EventsInvite’. That is the VF page name that I used in the unmanaged package. I strongly recommend renaming this page to whatever your naming convention demands before using it here.
  4. Then edit your event page layout(s) to place this custom quick action under the ‘Salesforce1 and Lightning Experience Actions’
  5. Now you are all set to add invitees to your events from Salesforce1 app


  1. The code is valid as of Spring ’16. If Salesforce provides this capability out of the box in the future, you should use the standard feature rather than this custom approach.
  2. I haven’t tested this out extensively, so please test before using it in production. Also, this code comes with no support or warranty. So, if something breaks in the future, feel free to leave a comment here, but there is no guarantee that I will respond or solve it right away

And, the fine print.. At the time of writing this blog, I am employed with Salesforce as an Architect. However, any code samples and declarative approach provided here are purely for experimental purposes and comes with no warranty or support. Matter of fact, all opinions and approach provided in this blog are purely my own and has nothing to do with my employer. It is assumed that you have the right Salesforce configuration and coding skills and will use the ideas presented here as you see fit. The primary purpose of this article is just to share the knowledge and my own experience. Nothing more, nothing less. Use this approach at your own risk

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.