The email infrastructure
for autonomous onboarding workflows.
Developers building onboarding agents need primitives to send welcome sequences, share credentials securely, and track completion. Mailgent provides the email API and encrypted vault so your agent can onboard users from day one without manual intervention.
API Primitives used
mail.sendSend welcome emails
Deliver onboarding emails — welcome messages, setup instructions, and checklist reminders — from your agent's identity.
mail.list_messagesTrack responses
Monitor for replies and completion confirmations. Detect when a user is stuck or needs help.
vault.storeStore credentials
Save provisioned account credentials in the encrypted vault. Retrieve them securely when needed.
mail.replyFollow up in-thread
Reply to existing onboarding threads with next steps, keeping the entire flow in one conversation.
Onboarding is a checklist nobody finishes on time.
New employees and customers need accounts provisioned, credentials shared, documentation sent, and setup steps completed — all within a tight window. When this process depends on humans remembering to send emails and check progress, steps get skipped and people fall through the cracks.
Developers building onboarding agents need email primitives to send sequenced messages and a vault to store provisioned credentials. Mailgent provides mail.send for outbound sequences, mail.list_messages to track progress, vault.store for credential handoff, and mail.reply to nudge users who stall.
How to build it.
mail.sendSend the welcome sequence
Your agent sends a welcome email with initial setup instructions using mail.send. It schedules follow-up messages for days 2, 3, and 7 with progressive steps.
vault.storeProvision and store credentials
The agent provisions accounts in your systems, then stores the credentials in Mailgent's encrypted vault using vault.store. Credentials are shared securely rather than sent in plaintext email.
mail.list_messagesTrack and follow up
The agent checks for replies with mail.list_messages. If a user confirms completion, it moves to the next step. If they go silent, it sends a reminder using mail.reply.
Example prompt
“Onboard the three new engineers starting Monday. Send welcome emails, provision GitHub and Slack accounts, store their credentials in the vault, and check in on day 3 if they haven't completed setup.”
What developers build.
Employee onboarding
Build agents that send IT setup guides, provision tool access, store credentials securely, and follow up until every checklist item is complete.
Customer onboarding
Build agents that welcome new customers, send product setup guides, and trigger escalation to a success manager if activation milestones are not hit within the first week.
Vendor onboarding
Build agents that collect tax forms, banking details, and compliance documents from new vendors via structured email sequences.
Trial-to-paid conversion
Build agents that guide trial users through setup, answer configuration questions, and send targeted emails to drive activation before trial expiry.
Why not use an HR platform's onboarding module?
HR platforms handle the human side — offer letters, benefits enrollment, org charts. They do not send technical onboarding emails, provision developer tools, or store credentials securely. The gap between HR onboarding and technical readiness is where people fall through.
Mailgent gives you the primitives to close that gap. mail.send delivers the sequence, vault.store handles credentials, and mail.list_messages tracks who completed what. Your agent owns the workflow end-to-end.
Encrypted credential handoff
Provisioned credentials are stored in AES-256-GCM encrypted vault — never sent in plaintext email.
Identity isolation
The onboarding agent has its own identity. It cannot access production systems or other agent mailboxes.
Audit trail
Every email sent and credential stored is logged. Compliance can verify who received what access and when.