Adobe made more than 70 of its tools callable from inside Slack
Firefly, Photoshop, Premiere, Acrobat and the rest now answer requests in a thread, routed by a bot that reads the surrounding conversation.
Adobe has made more than 70 of its applications callable from inside Slack through an app it calls Adobe for Slack. Firefly, Photoshop, Premiere, Acrobat, InDesign, Illustrator, Stock, Lightroom and Express are all included.
A user describes what they want in a thread and a bot routes the request to the appropriate application. It reads the surrounding conversation, so it can turn material already in the thread into PDFs, images or video, and pull assets from previous campaigns back into the chat for editing.
The interesting part is the routing
Seventy applications is a distribution announcement. The routing is the product.
Adobe's actual problem is that most people in a company that pays for Creative Cloud cannot use Creative Cloud. A marketing manager who needs a deck asset resized does not open Illustrator; they ask a designer, and the request queues behind work that matters more. That queue is where a large amount of organisational time goes.
An interface where the request is a sentence in the thread where the work is already being discussed removes the queue for the trivial half of it. The context-reading matters for the same reason: the material is usually already in the conversation, and having to find and re-upload it is most of the friction.
What it says about where interfaces are going
This is the second significant instance this fortnight of a vendor deciding its application is not where the work happens.
Adobe put 70 tools inside Slack. Anthropic added a browser to the Claude desktop app so the model can handle web tasks in a side panel. xAI expanded Grok Bot into a persistent agent that keeps working while the user is offline, available through Cursor as well as its own surfaces.
The common assumption is that the chat thread — or the agent — is the interface, and the application is a backend that gets called. For Adobe that is a substantial concession, because its business has been built on the applications being the destination.
It is also the right call. A company whose tools cannot be reached from where work is coordinated will lose the trivial requests to whatever can, and the trivial requests are the volume.
The security surface this creates
MCP-mediated tool access from a chat platform is precisely the architecture that produced this month's security problems.
An authentication bypass in LiteLLM's MCP handling was actively exploited in early September, giving attackers access to connected tools and services. Simon Willison observed on 30 August that ChatGPT Work now closes all three sides of the prompt injection "lethal trifecta": access to private data, exposure to untrusted content, and a way to act externally.
A bot that reads Slack threads and calls applications with a company's asset library attached has the first two of those. What it can do with them depends on the permissions Adobe grants it, and Adobe has not published the permission model, whether the bot can be reached from channels containing external participants, or what happens when a thread contains instructions rather than a request.
The commercial logic
Adobe also acquired Rilo, an Indian startup automating marketing and go-to-market workflows, on 3 September. Both moves point the same way: the company is repositioning from tools a specialist opens to capabilities other software calls.
Adobe has not said whether Slack access requires existing Creative Cloud seats, which determines whether this expands the licence base or just makes existing seats easier to use.
Runs the newsroom. Rename this profile in the studio to your own byline.
Related
Every weekday, the AI stories that moved money or shipped code.
No cross-posting, unsubscribe anytime. See all newsletters