Keep your API keys and integrations secure

When you connect Teamopipe to Zapier, an AI assistant or your own code, access runs through a workspace API key. A key can read and change your CRM data, so treat it like a password.

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.

Create keys safely

1. Go to Settings → Integrations and find API keys.
2. Click Create new key.
3. Enter a descriptive label in API key label, for example "Zapier production". The label is how you will recognise the key later.
4. Click Create key and copy the key straight into the service that needs it.

Good habits:

• Create a separate key for each integration, so you can revoke one without breaking the others.
• Don't paste keys into email, chat, tickets or shared documents.
• Store keys in a password manager or a secrets manager, not in source code or a spreadsheet.
• Rotate keys regularly, and revoke any you no longer use.

Key management is admin-only.

Revoke a key

1. Go to Settings → Integrations → API keys.
2. Find the key the integration uses and click Revoke API key.
3. Confirm with Revoke key.

Revoking is immediate and can't be undone. Every Zap or script using that key stops working at once, so find out which workflow depends on it first. If you are rotating a key, create the new one and update your integrations before revoking the old one.

If a key may be exposed

1. Revoke the key right away.
2. Create a replacement and update the legitimate integration.
3. Check your CRM records for unexpected changes.

If you contact us about it, send the key's label and roughly when you created it. Never send the key itself.

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 GDPR, data storage and privacy.

Related articles: API access — getting your key and what you can do with it, connect Teamopipe to Zapier, what Teamopipe API endpoints are available.

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 — we typically respond within 4 hours on business days.