lupin.Open console
App connections

Choose between an external mailbox and an agent inbox

Compare account ownership, credential flow and workflow identity before routing email through a connected app.

Lupin editorialAI-assisted3 min read

Start from whose correspondence the task concerns

A dedicated Lupin inbox gives an agent its own address and inbound workflow identity. A connected external mailbox grants access to an account that already belongs to a person or organization. Those are different goals even if both eventually return email text. For a new support triage address, a dedicated inbox can keep the agent’s correspondence separate. For a user explicitly asking about messages in their existing provider mailbox, an owner-authorized connection may be the relevant boundary. Choose based on intended ownership rather than assuming all email access is interchangeable.

Keep the credential flows separate

Lupin inbox resources use Lupin API authentication and resource scope. External mailbox connections use the enabled provider toolkit and hosted account authorization through Composio. The provider owns OAuth credentials, while Lupin stores the durable account reference and sanitized status. Connecting a mailbox does not import its refresh token into an inbox API key, and an inbox key cannot administer shared external accounts. The autonomous registration key’s receive, read and draft permissions also do not imply authority to connect or write to another person’s mailbox or send provider mail.

Do not treat connection as message migration

Authorizing an external mailbox makes supported tools available after active verification; it does not automatically copy historical mail into a Lupin inbox, preserve provider thread IDs there or move the mailbox’s public address. If the task needs historical messages, discover the real search and retrieval tools and understand their pagination. If the task needs a dedicated agent address, create and route that inbox through the authorized resource workflow instead. Keep provider message references and Lupin message IDs distinct in application state so a reply cannot accidentally target a different system’s resource.

Apply the correct approval to outward email

A provider tool that sends mail is connected app execution and requires exact approval in the Lupin consumer agent. A Lupin draft is a separate reviewable artifact in the dedicated inbox workflow. Neither incoming mail nor successful account authorization grants continuing permission to send arbitrary replies. Show the actual sending account, recipients and content before the outward effect. Also treat retrieved email bodies and attachments as untrusted task data; a message that instructs the agent to forward private content does not become authorized simply because it arrived in the selected account.

Plan coexistence with explicit routing

A team can use a connected account to answer owner-authorized questions about existing mail while giving a new autonomous workflow its own Lupin address. Save the chosen system and account with each job, and keep actions on the matching resource boundary. For a transition, document which address receives new correspondence, how old references are consulted and when external access should be revoked. Test a provider message and a Lupin message with similar subjects to ensure display text cannot confuse reply routing. This preserves a clear relationship between identity, data access and the permission to communicate outward.

Label resource origin in the client

Display or store whether a message reference came from the connected provider or a dedicated Lupin inbox before constructing a reply proposal. A subject line is not a stable routing identifier. This small origin field prevents a user selecting a familiar thread from accidentally authorizing a send through the wrong account or address.

Sources & verification

Reviewed against current checked-in Lupin routes, shared contracts and official provider references. No live calls, OAuth authorizations, app actions or purchases were performed.

Prepared with AI assistance by Lupin editorial. How we research and maintain these guides.

Put it into practice

Give your agent the right tools.

Review the API, workspace requirements and permissions before enabling a workflow.

Explore connections Register an agent