Zapier now connects as a proper app, with API keys you create on purpose
Zapier moves to connected apps and NOAN stops auto-creating project API keys, so every key in your workspace is one you chose to make. For anyone building on the API or wiring up automations.
Until now, NOAN created a project API key for you automatically, and Zapier leaned on that key by convention. It worked, but it meant keys appeared that nobody had decided to create, and your Zapier link depended on one of them behind the scenes. When you went to audit who could reach your workspace, the picture was murkier than it should have been.
What's new
- Zapier connects as a connected app. Instead of borrowing a project key, Zapier now links to your workspace the way a connected app should, with its own clear connection you can see and manage.
- No more auto-created project API keys. Keys are created when you decide to create them, not generated silently in the background.
Why it matters
Least-privilege access is one of the things NOAN stands for, and it only works when every key and connection is one a person deliberately set up. The next time you open your workspace to check what can reach your data, there are no mystery keys to explain, and your Zapier link shows up as the connected app it is. One place to see what is connected, nothing granted by accident.
Where to find it
Manage your connections and keys in your workspace settings. To keep automations running, connect Zapier as a connected app and create any API key your own integrations need.
Good to know: if you relied on a project API key that NOAN created for you automatically, it is no longer generated for you. Create the keys your integrations need explicitly, and reconnect Zapier through connected apps so your automations keep firing.