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.
Machine-to-machine access tokens are JWTs signed by Scalekit. Your API verifies signatures using the published JWKS at /keys, then authorizes requests using the scopes embedded in each token. This cookbook ties those ideas together end to end.
When your customer’s identity provider pushes more users than your plan allows, SCIM won’t stop it. This cookbook shows how to track provisioned users per organization, block creation when the quota is hit, and notify admins — using two webhook events and a counter in your database.
Build a GitHub PR summarizer that ranks the most-discussed pull requests in a repository and writes plain-language summaries. The secure version of this recipe binds each GitHub connection to a server-side session and never accepts a user ID from the browser.
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 and how you call Calendar and Gmail through built-in tools — without talking to provider APIs yourself.
