Keep your API keys and integrations secure
When you connect Teamopipe to Zapier or call the API directly, access runs through a workspace API key. This explains what that key can do, who can manage it, how to turn it off, and how your data is handled — so you can connect other tools with confidence.
What an API key can access
A Teamopipe API key acts on your whole workspace: through the API it can read and write the same records you can — deals, contacts, organizations, and tasks. It does not give access to your Gmail mailbox, your Google account, or the content of your emails. Teamopipe's Gmail permissions are separate and are never shared through the API or Zapier.
Who can create and manage keys
Key management is admin-only. You generate and delete keys in Settings → Workspace Settings → API keys. Because a key carries workspace-wide access, treat it like a password: don't paste it into shared documents, and where you can, create a separate key per integration so you can revoke one without breaking the others.
How to revoke access
- Open Settings → Workspace Settings → API keys.
- Find the key the integration uses and delete it.
- Any Zap or script using that key stops working immediately. Reconnect with a new key if you still need it.
Note: deleting a key can't be undone, and it affects every workflow using that key at once. If you're rotating a key, create the new one and update your integrations before deleting the old one.
Data handling and privacy
Data moved by Zapier passes through Zapier's platform under its own security and privacy terms; inside Teamopipe, API access is limited to your own workspace's records. For where your data is stored and how it's processed, see our GDPR, data storage, and privacy article. If you have a specific compliance question, reach out and we'll answer it directly.
If you're unsure about a connection or need to lock one down quickly, use the chat in the bottom-right corner or the contact form at teamopipe.com/en/contact — we typically respond within 4 hours on business days.