Skip to main content

Documentation Index

Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Zapier uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.

​
At a glance

Provider namezapier
Display nameZapier
Auth typeAPI key
HeaderAuthorization: Bearer <key>
Proxy hostapi.zapier.com
Env varZAPIER_API_KEY
Where to get a keyhttps://developer.zapier.com/api-keys

​
Get a key

Create an API key in the Zapier dashboard at https://developer.zapier.com/api-keys.

​
Log in

uvx authsome login zapier
A local browser form opens at http://127.0.0.1:7998. Paste the key into the masked input and submit. On a headless machine without a graphical session, authsome falls back to masked terminal input via getpass. The browser bridge is skipped automatically when no display is available. Verify: 
uvx authsome get zapier --field status
# → connected

​
Use the key

Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator. 
uvx authsome run -- python my_agent.py
Under the proxy, authsome sets ZAPIER_API_KEY=authsome-proxy-managed in the child’s environment and injects the real key into outbound requests to api.zapier.com. The child process never sees the actual value.

​
Multiple keys

Pass --connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern. 
uvx authsome login zapier --connection personal
uvx authsome login zapier --connection team

​
Rotate or remove the key

uvx authsome login zapier --force          # rotate
uvx authsome logout zapier                  # remove local credential
uvx authsome remove zapier                  # remove all local state for the provider
API-key providers have no revocation endpoint, so revoke and remove are equivalent for Zapier.

​
Override the bundled definition

uvx authsome inspect zapier > ~/.authsome/providers/zapier.json
# edit fields
uvx authsome list   # source now shows "custom" for zapier
See Provider schema for every field.

​
What’s next

Run agents with the proxy

Keep the key out of the agent’s environment entirely.

Multiple connections per provider

Keep two or more keys on the same provider side by side.

API-key providers

All bundled API-key providers.

Provider schema

Every field in a provider definition.