Apify Actors run in isolated containers with no persistent session — there is no concept of “who is logged in.” This recipe shows how to use Apify’s built-in user identity as the key into Scalekit’s OAuth token vault, so each user who runs your Actor connects their own third-party accounts, and tokens survive across runs without any user-managed input fields.
Install the Scalekit Auth Stack plugin into your coding agent and paste one prompt. The agent scaffolds OAuth handling, token management, and connected account logic so you can start writing agent logic immediately.
Connecting an agent to two external APIs means handling two separate OAuth tokens, two authorization flows, and two different error surfaces. This recipe shows how Scalekit manages the OAuth lifecycle for both connectors, then demonstrates two patterns for calling those APIs: fetching a token and calling the REST API directly, versus letting Scalekit execute the call through a built-in action.
