How do I disconnect my account?

Disconnecting from ApifyForge depends on which connection flow you used. If you connected via the browser token flow (paste a scoped token into Settings), there is a stored token to delete. If you used the CLI flow instead (npx apifyforge run <tool>), there is no stored token — only a local CLI session on your machine. Either way, the cleanest revocation path is to revoke the token in Apify itself, because that works regardless of which flow you used and takes effect immediately.

If you used the browser token flow

This is the common case. You have a scoped Apify API token AES-256-GCM-encrypted in the ApifyForge PostgreSQL database. To fully disconnect:

1. Delete the token in ApifyForge — open Settings → Apify API Token and click Delete token. This clears the encrypted_token column from your user row and prevents ApifyForge from running anything on your Apify account going forward. Any in-flight runs complete, but new runs fail with a 'no token configured' error and the dashboard reverts to the ConnectTokenStep state.
2. Revoke the token in Apify — open console.apify.com/settings/integrations, find the token you created (the suggested name was apifyforge-dashboard), and click Revoke. This invalidates the token on Apify's side, so even if the encrypted copy somehow leaked, it would be useless. Always do this step. It is the definitive off switch.
3. (Optional) Sign out of the dashboard — click Sign Out in Settings. This ends your OAuth session with GitHub or Google. Your dashboard account remains on the ApifyForge side but has no active session.

The order matters only slightly: revoking in Apify first guarantees the token is dead everywhere even if ApifyForge is unreachable, which is the safer default.

If you used the CLI flow

If you chose to keep your token entirely on your own machine via the CLI, there is no stored token on the ApifyForge server to delete. To disconnect:

1. Clear the CLI session — run apifyforge logout in your terminal. This removes the cached dashboard session credentials from your local configuration so the CLI can no longer upload results.
2. Remove the token from your local environment — delete the APIFY_TOKEN entry from your .env file or unset the environment variable. This is managed by you, not by ApifyForge.
3. (Recommended) Revoke the token in Apify — at console.apify.com/settings/integrations. Even though the token never left your machine, revoking it in Apify is still the cleanest way to make sure it cannot be reused.
4. (Optional) Sign out of the dashboard — same as above.

What gets cleared, and what doesn't

When you disconnect, the following happens on the ApifyForge side:

• Your encrypted token (if any) is deleted from the database.
• Your cached analytics data — revenue figures, failure rates, Fleet Health Score, Action Plan, week-over-week trends — is cleared from the ApifyForge cache.
• Your dashboard resets to the initial empty state (ConnectTokenStep).

Your Apify account itself is completely unaffected — disconnecting from ApifyForge has zero impact on your actors, runs, datasets, schedules, or anything else on the Apify platform. If you had a budget alarm set in Apify, it remains in place. If you had webhooks set up on your actors, they remain in place (ApifyForge never touched them).

Your ApifyForge dashboard account itself (your GitHub/Google OAuth link) remains unless you explicitly delete it. There is no self-serve account deletion yet; if you want to fully wipe your ApifyForge user row, contact support.

Reconnecting later

Reconnecting is straightforward. Sign back in with GitHub or Google, go to Settings → Apify API Token, paste a fresh scoped token (follow the create-apify-api-token walkthrough again), and click Save. Your dashboard repopulates as soon as you click the Run Fleet Analysis button. No previous cached data is restored — everything is pulled fresh. There is no penalty for disconnecting and reconnecting; you get a clean start every time.

For more on the security model and why we store the encrypted token at all, see Do you store my API token?.

Last updated: April 14, 2026