Connect your Apify account to an ActorConsole workspace to load Actors, run builds and workflows, and publish changes. You need an ActorConsole account and access to the Apify account that owns your Actors.
Steps
- Sign in to ActorConsole and select the target workspace in the top-bar switcher. Open Developer → Apify connection.
- Sign in to Apify Console as the Actor owner, or switch to the organization that owns them. Open Settings → API & Integrations using the link below.
- Create a separate API token named ActorConsole, or copy an existing one. To edit and publish Actors, use an unscoped token; limited tokens cannot modify Actors.
- Paste the complete token into Apify API key and click Connect Apify. If Console access is already connected, choose Add API key first.
- Wait for the Actor sync result, then click Check connection now. Confirm API operations is Valid and the displayed Apify account matches. Open Actors to check your portfolio.
Choose the right account and token permissions
Use an Apify API token here, not an ActorConsole API or MCP credential. Name a dedicated token ActorConsole so you can replace or revoke it independently.
For an organization, create or copy the token while that organization is selected in Apify Console. Your organization role must allow the actions you want to perform.
A scoped token can restrict reads and runs to selected resources, but Apify does not allow scoped tokens to create or modify Actors. Editing listings and publishing require an unscoped token. Successful validation alone does not confirm permission for every operation.
Optional: add Console access with the Chrome extension
- Install ActorConsole Apify Connector using the Chrome Web Store link in this section.
- Open the extension sidebar, choose Sign in with ActorConsole, and select Authorize browser on the page that opens.
- Sign in to Apify Console in Chrome and reload it so the extension can detect your account.
- Choose the same ActorConsole workspace and matching Apify account in the extension sidebar. Connect and approve cookie access when prompted.
- Return to Apify connection and click Check connection now. Confirm Console operations is Valid as well as API operations.
If ActorConsole cannot detect the extension, refresh the connection page after installation. Console-only access does not load your Actor portfolio or enable actual Actor publication; keep your API key connected.
Alternative: connect a Console session manually
- In Apify connection, choose Connect Console session or Replace cookies if available. Expand Connect manually with a resume cURL or cookie export and choose Resume cURL.
- In the signed-in Apify Console tab, open browser DevTools → Network and reload the page. Find the request to https://console-backend.apify.com/public/authentication/resume and choose Copy as cURL.
- Paste the copied request into the manual connection field and save. If you cannot find the request, use Domain exports and paste exports for console.apify.com and console-backend.apify.com into their labeled fields.
- Run Check connection now to validate the Console session. Use the same Apify account as your API key.
The backend export must contain ApifyRT from console-backend.apify.com; unrelated requests or frontend cookies will not work. Only the supported session value is retained. Treat the copied request as a password and reconnect when the session expires.
Fix a failed connection or an empty Actor list
- The save button is disabled: paste the full API token without quotes. The field requires at least 20 characters. Leave the optional Console fields empty for API-only setup.
- API operations is Invalid or Expired: create or copy a working token in Apify Console, choose Replace API key, save, and run Check connection now. Replace only the failing credential.
- API operations is Valid but an action is denied: check the token scope, your organization role, and access to the affected Actor. A scoped token cannot edit or publish Actors.
- The account does not match: check the selected workspace and the account shown on Apify connection. API and Console credentials must refer to the same account. For a different owner, use another workspace or disconnect and reconnect deliberately.
- Connected but no Actors appear: wait for the initial sync result, confirm the owner in Apify Console, and clear search and readiness filters on Actors. If the initial sync failed, save the working API key again with Replace API key to retry it.
- Some Actors were skipped or the workspace is restricted: review the sync message and workspace plan limits. API authentication can succeed while the portfolio requires Pro.
- Console data is missing: validate Console operations separately. Reconnect an expired browser session; an API key alone does not provide account costs or creator revenue.
Replace a key or disconnect the workspace
To rotate a token, create or rotate it in Apify Console, then choose Replace API key in ActorConsole, paste the new value, and save. Check the connection and Actor sync before retiring the previous token. Replacing the API key keeps the Console credential unchanged.
Disconnect credentials removes both saved credentials from this workspace and stops ActorConsole operations until you reconnect. It does not delete your Actors or resources in Apify. Revoke an unwanted token separately in Apify Console.