How do I disconnect or revoke the Drip integration?

Last updated May 20, 2026Integrations

Removing the Drip integration from Valid Email Checker is a two-step process for full hygiene. Step one: delete the connection on our side. Step two: revoke the API token inside Drip. Step one stops VEC from accessing Drip; step two ensures the token cannot be reused even if it was copied elsewhere.

Step 1: delete the connection in VEC

Sign into VEC and open Integrations.
Find the Drip row in the Connected Integrations table.
Click the three-dot row menu and pick Delete.
Confirm the action in the modal.
The Drip entry vanishes from the table immediately.

Deleting the connection also clears the sync history bound to it. Past verification jobs remain in Uploads & Results as independent records.

Step 2: revoke the API token in Drip

Sign into Drip.
Open Settings → User Settings → API Tokens.
Find the token you used to connect to Valid Email Checker.
Click the revoke or delete icon next to the token. Drip instantly invalidates it.

Why revoke separately

Deleting on our side removes our stored copy of the token. The token string itself is still a valid Drip credential unless you revoke it. If the token was ever shared with a contractor, used in a script, or stored elsewhere, regenerate for a clean slate. Drip exposes per-token request logs, which makes it easy to verify VEC is no longer touching your account.

Multi-account considerations

If you manage multiple Drip Account IDs (typical for agencies handling several e-commerce brands), each VEC connection points at exactly one Drip Account. Disconnecting one connection does not affect the others. The per-account isolation makes it safe to disconnect a specific client without impacting the rest.

What happens to running verifications?

A verification mid-import keeps running using the cached credentials. New sync attempts fail immediately until you reconnect. To get going again, walk through the connect flow in the Drip integration guide.

Reconnecting later

Go to Integrations → Connect Integration → Drip, paste a fresh token, and supply the Account ID. The new connection is treated as fresh. If you previously named it something distinctive (recommended in multi-account workflows), reuse the same name for team-facing consistency.

Team-member-created connections

A small Users icon next to the provider name marks a connection created by a team member. Owners can delete any connection; team members can delete only their own.