How Adobe I/O Events Boosts Collaboration in the Slack + Creative Cloud Integration

Creative Cloud workflows are now even more collaborative, thanks to Adobe I/O’s lightning-fast event-driven integrations. In addition to the revamped app for Microsoft Teams, CC also integrates with popular team communication tool Slack (check out the Creative Cloud for Slack app). Leveraging the power of Adobe I/O Events, subscribers can now seamlessly share, preview, communicate and collaborate on creative content created on CC across devices, locations, and functional teams.

“Creative Cloud users can just paste a link of the CC asset, shared via adobe.ly and xd.adobe.com, in Slack,” explains Adobe product manager Siddharth Arora. “It provides rich context such as unfurls, which makes it easier to collaborate.”

Unfurls (or rich image previews) make it easier to discuss designs in detail either publicly or one-to-one without leaving Slack, letting users add more context when an asset is shared. Adobe Creative Cloud for Slack generates app unfurls for major CC file types, which allow for more control over the unfurling than classic unfurls (which just use Open Graph or Twitter Card metadata to render an approximation of the content). They also enable users to add interactivity through buttons or message menus.

The Slack integration enables you to instantly preview Creative Cloud assets.

The real benefit, for the Adobe I/O Events team at least, is in the app’s notification abilities. Creative Cloud for Slack notifies users of any comments that are being left on their CC files, such as XD prototypes and design specs, to keep them up to date and ensure they don’t miss a valuable piece of feedback, a process made much more effective by an event-based integration.

How Adobe I/O Events powers Slack notifications of Creative Cloud activities

As I/O Events (JSON objects that describe something that happened) call pre-defined webhooks within mere seconds of the comment or new file being added, everything is done in real time and there’s no need for polling — allowing for a more scalable and decoupled architecture. Whenever an event gets triggered, the application is notified through an HTTP POST request.

Using Adobe I/O Events payloads, the team was then able to surface events in Slack, like delivering ‘left a comment’ and ‘replied to the comment’ events to users when a comment is made in Adobe XD.

Adobe I/O Events exposes events published by Adobe services, so that client apps (written by Adobe, partners, system integrators, independent software vendors, and customers) can subscribe to and receive those events. The idea is that anyone can build apps that react to Adobe events, and in turn call Adobe APIs (or execute serverless code). Besides Creative Cloud, I/O Events are also available for Adobe Experience Manager, Adobe Analytics, and Cloud Manager, and there are more to come in the near future.

Notifications make use of Events I/O to ensure users stay up-to-date.

Events are also sent to authorized applications, and if Slack is being used in another language, (such as Japanese, Spanish, German, or French), the app will send messages and respond to users in their preferred language as well.

The new integration, powered by the Events I/O API, means creative teams can stay focused on producing beautiful, functional design, while making it easier to hand off work to stakeholders or other team members, keeping processes running smoothly with fewer interruptions and hiccups.

Follow the Adobe Tech blog for more developer stories and resources, and check out Adobe I/O on Twitter for the latest news and developer products.