Account for connection slots, pending setup and tool costs
Understand pending capacity reservations, creation usage and unbounded tool effects before planning integration costs.
Lupin field guides
App connections
OAuth, connected accounts and external application tools.
20 published articles
Approve apparent reads as well as writes in connected apps
Use actual tool behavior, account identity and exact arguments to authorize connected application execution.
Choose between an external mailbox and an agent inbox
Compare account ownership, credential flow and workflow identity before routing email through a connected app.
Choose OAuth scopes from the workflow’s actual needs
Map desired operations to provider scopes, inspect the auth blueprint and reauthorize deliberately when access changes.
Connect an app through its owner’s hosted authorization
Discover an enabled app, preserve the connection attempt and verify active ownership after hosted authorization.
Debug a failed connected app tool without broadening access
Follow the controlled execution boundaries and preserve operation evidence before reconnecting or retrying.
Discover an app tool’s real schema before proposing an action
Search account-scoped tools, inspect input schemas and retain the discovered revision before requesting approval.
Find the apps that your Lupin workspace can actually connect
Search the enabled catalog, interpret readiness and paginate instead of assuming every provider integration is available.
Handle tool pagination and large app results deliberately
Follow the correct cursor contract, bound the task and separate tool inventory pages from provider data pages.
Integrate Google Workspace with HTTP or connected app tools
Choose a credential boundary and map Gmail and Calendar tasks to their real APIs without inventing a generic Workspace endpoint.
Keep an audit trail for connected tool sources and approvals
Record selected account, discovery version, exact approval and operation outcome without collecting OAuth secrets.
Map connection permissions to the action being authorized
Separate workspace scope, lifecycle privileges, tool discovery and exact action approval instead of using one connected flag.
Migrate an app integration through owner reauthorization
Preserve account intent and task semantics while rebuilding authorization, tool schemas and pending actions on the new boundary.
Read connected account state through its full lifecycle
Interpret provider status, owner verification, reconnect replacement and upstream revocation as distinct lifecycle stages.
Recover a connection after provider authorization stops working
Distinguish inactive grants, insufficient scope and provider outages while preserving the replacement authorization lifecycle.
Recover an expired hosted authorization link safely
Distinguish link lifetime, account activation and uncertain creation before deciding whether to reconnect.
Resolve app authentication setup before starting OAuth
Distinguish authentication blueprints, provider credentials and customer consent when an integration is unavailable.
Retry connected app tools without creating duplicate effects
Retain operation identity, concrete arguments and provider evidence across timeouts and durable recovery.
Route connected app discovery and execution through MCP
Keep account-scoped discovery, pinned execution and client-side authorization intact across the MCP boundary.
Select a connected account before discovering or approving tools
Bind the intended account to the task, revision and approval so display names cannot silently reroute work.