Workplace has an Integrations Directory where customers can discover and install integrations to make Workplace more useful for them. The directory features third party integrations that have been built by developers of enterprise SaaS (Software as a Service) tools, and each integration in the directory has been vetted by the Workplace team before launching to customers.
If you're a developer building an enterprise productivity tool, and you'd like to integrate with Workplace, we want to hear from you! Request an app today via our support tool, and a member of the Workplace team will get in touch with you to get you up and running.
It is not necessary to register your interest in order to build Custom Integrations.
If you are a system admin in a Workplace Premium community, you can create a custom integration for your community at any time.
Once you've registered your interest to develop an integration for Workplace, a member of the Workplace team will create an app ID for you that you can use for development.
You'll need to provide the User ID of a Facebook user who can be added as a Developer on the app, so that you can modify the app via developers.facebook.com/apps.
Once you've been added as a developer, you'll need to configure the following values:
Note: We'll manually be verifying and approving this information before your app will be made visible to any customers.
To be part of the Integrations Directory, you will need to supply the following information:
More information on what to provide can be found below.
A string which represents your app's name. This will be visible in the directory and wherever your app is referred to. If your integration has a bot, this will also be the bot's name.
Recommended Character Length: 30
A string that represents your company/organization. Will be used alongside the integration name to help people understand who is responsible for the functionality of the integration.
Recommended Character Length: 30
A short sentence description of what your integration does. This will be shown in the directory where we list multiple integrations together, and in the integration install dialog.
Recommended Character Count: 40.
A clear description of what your integration/app does and why people should install/enable it. This will use shown in your integration's directory listing.
Guidance: around 400 characters across up to two paragraphs.
A set of images that showcase what your integration does. You can include a mix of mobile and desktop screenshots.
You must supply at least 3 images. Maximum of 8.
Each image must be:
Once you've registered your interest to build a Workplace integration, you'll be provided with an app ID and access to a dashboard where you can configure the features your integration will support.
When you're ready to launch your integration, a member of the Workplace team will need to review your app before making it available in the Integrations Directory.
The review process consists of two stages:
During Functional Review, your app will be tested for compliance with the Workplace Platform Policy, then given a full functional test on one or more Workplace communities.
As part of the test, we'll verify that your integration uses the minimum number of required permissions to provide the functionality as described, and check that there are no privacy issues with how Workplace information is shown via your integration. You may be given feedback on your integration at this stage.
Once your integration passes functional review, Facebook will coordinate with an independent third party security vendor to give your app a security review, checking for common security pitfalls like Cross-Site Scripting (XSS) vulnerabilities.
Only on completion of a successful security review will your integration be launched to our directory.
As mentioned above, all apps in the directory will be subject to a review against the Workplace platform policies, which have been put in place to protect the security and functionality of Workplace for our customers.Workplace Platform Policies
While you should spend some time reading the full policy document, below are some guidelines to help you prepare for review as you develop your app.
Build integrations that make Workplace a safer and more useful place to collaborate.
Request only the minimum permissions necessary for your integration to be useful.
Follow all relevant local laws and industry regulations.
Provide meaningful customer support for you app, including a way for customers to easily contact you.
Localize your application strings according to the recipient user's
Harvest data from Workplace for use in another tool.
Use contact info (email, phone numbers etc) obtained from Workplace APIs for communication on another channel (e.g. mailing lists).
Emulate Workplace functionality.
Enable circumvention of group / community privacy rules.
Make data obtained from one Workplace Customer available to another Workplace Customer or aggregate data from multiple Workplace Customers together (for example, to create cross-Customer benchmarks or comparisons).
Violate the names or trademarks of other brands.
Message or tag all users once enabled, unless this is an admin-triggered feature of your integration.
Expose Workplace access tokens in any way (e.g. in the UI or in HTTP GET / POST parameters), either during app installation or in your admin surfaces.