ChatGPT Plugins Combine Tool Access With Task-Specific Workflows
Corey Ching argues that ChatGPT plugins can turn connected work systems into task-specific workflows: apps such as email, cloud storage, calendars and Slack supply context, while skills structure it into an output. In the examples shown, that means producing editable Canva flyer drafts or assembling a sales brief that surfaces a customer’s pilot scope, security dependencies, owners and approval deadlines before a meeting.
Plugins turn connected tools into a workflow inside ChatGPT
Corey Ching describes plugins as connections between ChatGPT and the systems where work already happens, including email, documents, calendars, cloud storage, and work chat. A plugin securely links an application to ChatGPT; skills provide a playbook for a job, such as structuring a report, preparing for a meeting, or guiding a repeatable workflow.
The directory shown includes common work tools such as Gmail, Slack, Google Drive, GitHub, Linear, Notion, Outlook Email, and Asana. The important distinction in Ching’s framing is between access and process: connected apps provide material to work with, while skills guide how that material is used for a particular task.
With plugins, you can apply this same pattern: gathering context, doing some work, and producing an output to any type of task, all inside ChatGPT.
The output can remain editable in the tool where it belongs
A design request illustrates the intended workflow. A user asks ChatGPT to make an event flyer in Canva for a student science fair on Friday, in a “1950s retro-futuristic style.” The Canva plugin returns four editable flyer options and offers to add the selected design to the user’s Canva account.
The options include the event name, date, address, and copy such as “Tomorrow’s Big Ideas—Today!” Ching describes the result as a useful first pass: he likes the style, then can move into Canva to make edits. The demonstrated workflow uses ChatGPT to turn a conversational brief into design options, while leaving the asset editable in Canva.
A sales brief draws together email, files, and internal decisions
Corey Ching gives a more consequential example in meeting preparation. For an upcoming “Aster Peak review,” he asks the sales plugin to pull the relevant email, the latest proposal in Drive, and recent decisions from Slack. He asks for a meeting agenda, a breakdown of risks, and open questions.
The resulting brief brings together information shown as coming from Slack, Google Drive, Google Calendar, Gmail, HubSpot, and a cloud browser. It describes Aster Peak as interested in moving from exploratory AI use to a controlled enterprise rollout. The proposal shown in the brief is a 12-week pilot for 150 employees, centered on executive-briefing preparation, field-event planning, and internal investment reviews.
The brief frames the immediate sales task around implementation, security, and measurable business value rather than another general capabilities presentation. According to the displayed summary, Aster Peak’s VP of Digital Operations wants the review to focus on those questions, and the DevEx Blossom Team should seek alignment on pilot scope, success criteria, and a path through security and procurement.
The customer’s stated concerns are concrete: how company information will remain private and appropriately permissioned; whether the pilot can begin with a limited group; what implementation support will be provided; how adoption and productivity gains will be measured; and whether a September start is realistic. Aster Peak also asks to reserve time for Security and Procurement instead of spending the meeting on a general product walkthrough.
The central constraint is not interest but the path to approval
The preparation document places customer context beside internal conditions for proceeding. It records a decision to keep phase one limited to business and operations teams, with engineering workflows to follow later; to limit SSO and managed-workspace access to Aster Peak domains; and to require both an executive sponsor and an operational owner before kickoff.
| Decision or dependency | What the brief specifies |
|---|---|
| Pilot scope | 150 initial users and three business workflows; engineering workflows can follow later. |
| Security timing | A September start is achievable only if the security review begins by July 15. |
| Commercial terms | $275,000 pricing, with flexibility around user count and workshop structure. |
| Required ownership | One executive sponsor and one operational owner from Aster Peak before kickoff. |
| Meeting objective | Alignment on pilot workflows, security-review ownership and timing, and the commercial path to approval. |
The sharpest dependency is timing. The brief treats September as achievable only if the security review starts by July 15; it explicitly warns against presenting the date as guaranteed when it depends on security and contracting milestones. Its proposed response is to name security owners and schedule the technical review during the meeting.
The agenda is built around resolving those dependencies: confirm the desired decision and approval path, review the pilot workflows, address security and governance, agree on success measures, and establish procurement owners, deadlines, and the September target. Other risks follow from the same structure. Scope expansion could slow approval; productivity claims may not support final budget approval without baselines and measurement ownership; and executive interest may not produce sustained adoption without an accountable operational lead.
Ching says producing the brief saves time that he can use to review the material and prepare for the meeting. The generated brief is intended for review before ChatGPT saves it as a new document and shares it with the team.