Integrations · Email
A Guild agent emails you when a task finishes, hits an error, or needs your attention. Guild routes each message to the right person based on who started the session, enforcing that routing server-side without any configuration from you.
Book a demo
See how teams govern agents that use Email.
Start free
Connect Email and scope your first agent.
What the Email integration exposes
The integration provides thenotify_me_by_email_send tool. The tool sends an email to the person the agent works for, with a subject, a plain-text body, an optional HTML body, an optional sender name, and an optional PDF attachment up to 2 MiB. Recipients are capped at 20 emails per hour.
How it works
1
Install the integration package
Add
guildai~notify-me-by-email to your agent’s package.json dependencies. Import NotifyMeByEmailTools from @guildai-services/guildai~notify-me-by-email and spread it into your agent’s tools object.2
Call the send tool
Pass a
subject and text to notify_me_by_email_send. Optionally include html, a fromName up to 64 characters, or one PDF attachment as a base64-encoded content field with a .pdf filename.3
Confirm who receives the message
In chat and test sessions the email goes to the person who started the session. In schedule and event trigger sessions it goes to the person who installed the agent. Sessions with no person behind them return an error instead of sending.
Why Email tool access still needs governing
The Email integration requires no credential, so there is nothing to scope with credential policies. Guild records each tool call in the session log, giving you a trace of every notification an agent sent and the session that triggered it. For integrations that do use credentials, Guild’s credential proxy injects authentication server-side and enforces ALLOW and DENY rules before any request leaves Guild, so agents never see secrets.About the Email integration
The Email integration lets an agent send an email to the person it’s working for, for example when a task finishes or hits a problem. It’s built into Guild, so there’s no credential to connect and no external service to sign up for. The integration isguildai~notify-me-by-email.
Who receives the email
The tool always sends to one Guild user’s email address; the agent can’t choose the recipient.- Chat and test sessions: the person who started the session.
- Schedule and event trigger sessions: the person who installed the agent in the workspace.
- Sessions with no person behind them: no email is sent, and the tool returns an error. These include API trigger sessions, chat sessions started with an API key, and triggered sessions of an agent installed with an account API key.
Guild Notifications, or a sender name the agent sets, at Guild’s notifications address.
Usage
notify_me_by_email_send takes:
Tools
Tools in the latest published version ofguildai~notify-me-by-email:
Limitations
- Each recipient gets at most 20 emails per hour, counted from the first send in that hour; sends beyond that fail.
- One attachment per email, and it must be a PDF.
Frequently asked questions
Can an agent choose who receives the email?
Can an agent choose who receives the email?
No. The tool always sends to one Guild user’s email address determined by the session context. The agent cannot set the recipient.
Do I need to connect a credential or sign up for an email service?
Do I need to connect a credential or sign up for an email service?
No. The Email integration is built into Guild. There is no credential to connect and no external service to sign up for.
Can I attach files other than PDFs?
Can I attach files other than PDFs?
Not yet. The tool accepts one attachment per email, and it must be a PDF with a
.pdf filename, base64-encoded content, and content type application/pdf, up to 2 MiB.What happens if an agent sends too many emails?
What happens if an agent sends too many emails?
Each recipient can receive at most 20 emails per hour, counted from the first send in that hour. Sends beyond that limit fail.
Put an email-notifying agent in your workspace today
Book a demo
See how teams govern agents that use Email.
Start free
Connect Email and scope your first agent.