Before you begin
To do an organization rollout of Zapier in your ChatGPT workspace, you need:- A ChatGPT Business, Enterprise, or Edu workspace.
- The Owner role in your ChatGPT workspace. Admin is not enough: you need Owner, the role above it.
- A Zapier Enterprise account. Enterprise provides the workspace-level app access controls, SSO, and audit logging this rollout relies on.
- Every member provisioned into your organization and into a User Group with access to your workspace. Manage members and User Groups covers both requirements.
1. Turn on workspace capabilities
Your workspace must allow custom plugins before you can create Zapier as one.Open Workspace settings
Open Permissions
Turn on the plugin capabilities
- Use plugins
- Publish plugins to workspace
- Create plugins with MCPs, which is what lets you create the custom Zapier plugin.
Save your changes
2. Create the Zapier plugin
You create Zapier as a custom MCP server and save it as a plugin.Open Plugins in ChatGPT
Add a custom MCP server
Enter the name
Zapier.Enter the connect URL
Select OAuth
Accept the disclaimer
Create the plugin
3. Publish the plugin to your workspace
Until you publish it, the plugin is yours alone. Publishing shares it with your workspace, and it is also where you set which roles and tools the plugin covers.Open the plugin
Open Manage
Start publishing
Open Configure tools
Select Read tools and Write tools
Enable all new tools
Refresh the tool list
Confirm the tools
Review the risk panels
Publish
4. Install it for every member
Publishing makes the plugin available to your workspace. To push it into every member’s account, set its workspace default to Installed in the admin console.Open the admin console
Open Plugins
Open your organization's tab
Select Zapier
Set the availability
- Installed pushes Zapier to every member’s account, so nobody has to find or install it. The first time a member uses it, ChatGPT takes them to Zapier’s sign-in screen.
- Available only lists Zapier in your organization’s plugins, and each member finds and installs it themselves.
Turn off the setup capabilities (optional)
Create plugins with MCPs and Publish plugins to workspace were needed to set Zapier up, but members do not need them to use it. While they stay on, any member covered by them can create a plugin from any MCP server and publish it to your workspace. To close that off once Zapier is installed:Open Permissions
Turn off the setup capabilities
Save your changes
Connect as a member
Each member signs in to Zapier once, which creates their own MCP server connection. Tell them which Zapier workspace to select, because that workspace’s controls govern their connection. The Workspace app tab of the ChatGPT connection guide walks members through it. To limit which Zapier apps and actions members can use, set app and action restrictions on your Zapier account.Announcement you can send to members
Announcement you can send to members
WORKSPACE_NAME with the workspace your members select:Verify the result
- Check the plugin. In the admin console, open Plugins and select your organization’s tab. Confirm Zapier shows Enabled and its Workspace default is Installed.
- Check a second account. Sign in as a non-admin member and confirm Zapier is already installed.
- As a member, run one call. In a chat, ask
@Zapier which tools do I have available?. ChatGPT lists the Zapier tools available to that member. Any answer confirms Zapier is working, even if the member has not connected any apps yet.
If Zapier does not appear
- If the plugin is missing from the Apps page after you click Publish, refresh the page and wait. It can take a while to appear.
- If you cannot click Publish, review both risk panels on the publish page first.
- If a member cannot find Zapier, confirm their role has access to it, and check its availability under Customize per role.
- If availability is Available rather than Installed, the member installs Zapier themselves: Plugins in the ChatGPT sidebar, then your workspace’s tab.
- If Zapier is connected but tools are missing, learn how to troubleshoot missing tools in an MCP client.