Slack has always been the place where work gets talked about.

You send the brief. Someone drops a spreadsheet into a channel. A designer shares an early mockup. Marketing asks for a different version. Someone else replies three hours later with, “Can we make the headline a little bigger?” And somewhere in the middle of all that, the actual work gets done in a completely different collection of apps.

That separation is starting to look rather old-fashioned.

Adobe has now brought more than 70 of its creative and productivity tools directly into Slack, allowing teams to create, edit and transform images, videos, designs and documents without leaving the conversation. The new Adobe for Slack integration, announced September 2, is available globally to Slack Business+ and Enterprise+ customers across desktop, web and mobile.

And yes, that means Photoshop, Premiere, Illustrator, InDesign, Acrobat, Lightroom, Adobe Express, Firefly and Adobe Stock are now part of a Slack workflow.

Suddenly, Slack doesn’t just look like the place where you discuss the project. It can become part of the place where you actually make the thing.

The interesting part, though, isn’t simply that Adobe’s apps are available inside Slack. We’ve seen integrations between workplace software and creative tools for years. The bigger shift is that Adobe is connecting its tools to the context already sitting inside your Slack conversations.

That distinction matters.

Imagine a marketing team discussing a new product launch in Slack. The campaign brief is sitting in a Canvas, feedback is scattered across a channel, somebody has already uploaded product photographs and an old campaign asset is sitting somewhere in Creative Cloud.

Traditionally, turning all of that into something useful means jumping between Slack, Adobe apps, cloud storage and perhaps a spreadsheet or two.

Adobe’s idea is: why not just ask Slack?

With Adobe for Slack, users can talk to Slackbot, Slack’s built-in AI assistant, in natural language and ask it to pull relevant information from conversations, files, channels and Canvases. Slackbot can then call on Adobe’s tools to create or modify the content.

So instead of opening Photoshop and figuring out which file you need, you might start with something much closer to the way people actually work:

“Take the approved product image from this campaign, remove the background, resize it for our social channels and create a few variations.”

The idea is that Slackbot can coordinate the request with Adobe’s tools rather than making you manually shuttle files and instructions between applications.

That makes Slack feel less like a messaging application and more like a conversational workspace.

And Adobe is going considerably further than simply generating an image.

The company says Adobe for Slack can turn project plans and conversations into PDFs, images and videos. It can search Creative Cloud assets by subject, style or mood, help adapt approved campaign material for different channels, create designs from templates, transform spreadsheet data into shareable visuals or PDFs, and perform bulk image edits such as removing backgrounds, adjusting lighting, cropping and resizing.

For a team that spends its day moving information from one application to another, that could be the genuinely useful part.

Think about something as mundane as event photography.

A company has hundreds of images from an event. The marketing team needs headshots cleaned up, product shots resized and a selection of images prepared for social media. None of that is particularly exciting work, but it can eat up an afternoon.

If those images are already being discussed in Slack, the promise is that the team can start the task from that same conversation.

Someone can ask for the images to be refined. Adobe’s tools handle the actual creative operations. The results can then come back into the Slack conversation for everyone else to review.

And that last part is important.

Adobe isn’t really trying to replace Photoshop with a Slack chat window.

The company explicitly positions Adobe for Slack as a way to keep creative work moving during the early and collaborative parts of the process. When somebody needs pixel-level control or more sophisticated editing, they can continue working in Photoshop, Premiere, Acrobat, Firefly or other dedicated Adobe applications.

In other words, Slack becomes the front door rather than the entire house.

That’s probably the more sensible approach.

Professional designers aren’t suddenly going to abandon Photoshop because Slack can produce an image from a prompt. Creative work often requires far more control than a conversational interface can provide. But a huge amount of work happens before anyone reaches that level of precision: gathering references, discussing requirements, finding old assets, producing rough versions, requesting changes and getting approval.

That’s precisely the territory Adobe is targeting.

It also explains why the timing of this integration feels significant.

Workplace software is increasingly becoming conversational. Instead of navigating through menus, opening applications and learning where individual features live, people are increasingly describing the outcome they want and letting AI figure out which tools need to be used.

Adobe has been pushing aggressively in that direction.

Just weeks before the Slack announcement, Adobe introduced a similar integration for ChatGPT, bringing more than 70 professional creative and productivity tools from products including Photoshop, Firefly, Acrobat and Adobe Express into ChatGPT. Adobe says its broader strategy is to bring those capabilities into the AI platforms people already use, with Slack now joining ChatGPT, Claude and Copilot, while Gemini is planned for the future.

That puts Adobe in an interesting position.

For years, the company’s strength was that people came to Adobe when they wanted to create something. Now Adobe increasingly wants to meet people wherever they already happen to be working.

Slack is particularly valuable because it contains something a standalone creative application doesn’t necessarily have: context.

A Photoshop document knows what is inside the document. A Slack workspace can know why the document exists.

The conversation might explain that the product is launching next month. A teammate might have specified that the campaign should feel more premium. Someone else may have rejected an earlier version. The final approved logo could be sitting in another message. A Canvas might contain the actual campaign brief.

All of that information is potentially useful when creating the final asset.

Adobe’s Slack integration is therefore less about putting Photoshop inside Slack and more about connecting Adobe’s creative capabilities to the messy, conversational context surrounding the work.

That is a subtle difference, but arguably the more important one.

It is also where the use of MCP comes into the picture.

Adobe describes the integration as an example of MCP apps in Slack helping turn conversations into action. MCP, or Model Context Protocol, provides a standardized way for AI systems to connect with external tools and services. In this case, Slackbot can act as the conversational layer while Adobe’s tools provide the actual creative and document capabilities.

That architecture points toward a broader change in how workplace software could work.

Instead of thinking about Slack, Photoshop, spreadsheets, document editors and project-management software as completely separate destinations, AI assistants can increasingly sit between them.

You tell the assistant what you need. The assistant figures out which application or capability is appropriate, gathers the necessary context and coordinates the task.

It’s a little like having a coworker who knows where everything is, understands the conversation and can operate several different tools on your behalf.

Of course, there are still plenty of reasons to be cautious about that vision.

Creative work is subjective. A prompt that sounds perfectly clear to one person can produce something completely wrong for a brand. Context can also be misunderstood. Slack conversations are messy by nature, and not every comment, file or old version should automatically become part of a new piece of creative work.

There’s also the obvious question of how much control professionals will want to give an AI-driven workflow.

Adobe appears to understand that. The company isn’t suggesting that Slack should become a replacement for its full desktop applications. Instead, it is positioning the integration as a faster way to get from conversation to a useful result, while leaving the more demanding work inside Adobe’s dedicated tools.

That makes considerably more sense than pretending a chat interface can replace decades of professional creative software.

There’s another detail worth noting: you don’t necessarily need an Adobe account just to start using the Slack app. Adobe says users can begin as guests, while signing into or creating a free Adobe account unlocks additional tools and skills, generative AI capabilities, access to Creative Cloud files and continuity across sessions.

There is, however, a fairly important limitation at launch.

Adobe for Slack isn’t being offered to every Slack user. It’s available to Slack Business+ and Enterprise+ customers globally, which puts it firmly in the workplace category rather than making it a feature for the average free Slack workspace.

Still, the direction is hard to miss.

Slack began life as a better way for teams to communicate. Over time, it accumulated files, integrations, apps, workflows, project information and increasingly sophisticated AI features. Now Adobe is adding professional creative production to that pile.

And that changes the mental picture of what Slack actually is.

It isn’t just the digital office hallway where everyone talks about the work anymore. With Adobe sitting behind Slackbot, that hallway is starting to have a workshop attached to it.

You can discuss the campaign, pull up the relevant files, find an old Creative Cloud asset, create a new version, turn a spreadsheet into a polished document, make edits, ask for another variation and send the result back to the team — all without necessarily leaving the conversation that started the process.

That’s a pretty big leap from “Where’s that file again?”

The more interesting question now is where this trend goes next.

Adobe is already bringing its tools to ChatGPT, Claude, Copilot and Slack, with Gemini planned. Other creative companies are pursuing similar strategies, making their capabilities available through AI assistants rather than forcing users to visit a dedicated application every time they need something done. TechCrunch notes that companies such as Canva and Figma are also bringing creative capabilities into chatbot environments.

The software industry has spent decades convincing us that the application is the destination.

AI is increasingly suggesting that the destination doesn’t matter quite as much.

The conversation does.

And if that idea sticks, Slack may be remembered as one of the places where the transition became obvious: a chat window that started out helping people talk about their work, and gradually became capable of helping them create it, too.

I certainly didn’t expect Slack to become a design tool.

But here we are.