Who is Agentic Mail designed for?<\/h2>
Agentic Mail is aimed at developers, AI enthusiasts, and technically-minded business owners who want their email to be an active part of their automated workflows. Typical use cases include:<\/p>
- \n
- Building AI-powered inbox assistants or triage bots that react the moment a message arrives<\/li>\n
- Connect AI agents such as Openclaw or Hermes<\/li>\n
- Connecting Hostinger email to no-code\/low-code platforms (n8n, Make, Zapier) via webhooks<\/li>\n
- Programmatically sending transactional email and reading replies through the REST API<\/li>\n
- Controlling outbound email scope for automated mailboxes to prevent accidental spam<\/li>\n<\/ul>
Where do I find Agentic Mail in hPanel?<\/h2>
- \n
- Log in to hPanel at hpanel.hostinger.com<\/li>\n
- Click Emails in the left sidebar<\/li>\n
- Select the domain whose mailbox you want to configure<\/li>\n
- Scroll down the secondary sidebar and click Agentic mail<\/li>\n
- You land on the Overview page showing all available features<\/li>\n<\/ol>
What is a webhook and how does it work in Agentic Mail?<\/h2>
A webhook is a real-time HTTP push notification. When a configured event happens on your mailbox — currently message.received — Hostinger Mail immediately sends an HTTP POST request containing a JSON payload to the URL you specify. Your server or agent can then parse and act on that data without polling.<\/p>
Webhooks use Bearer token authentication. Your token is displayed only once, immediately after creation. Make sure to copy it before leaving the page — you will not be able to retrieve it again.<\/p>
How do I add a new webhook?<\/h2>
- \n
- Go to Agentic mail → Webhooks<\/li>\n
- Click the Add webhook button (top-right, purple)<\/li>\n
- Choose the mailbox to monitor from the dropdown<\/li>\n
- Enter your Webhook URL — must be a publicly accessible HTTPS endpoint<\/li>\n
- Trigger event is pre-set to message.received (the only available event)<\/li>\n
- Click Add webhook to save<\/li>\n<\/ol>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/05\/2026-05-19_09-26.png\")
<\/p>What does the “message.received” trigger event mean?<\/h2>
message.received fires when a new email lands in the monitored mailbox. Hostinger Mail sends the POST immediately after delivery, so your agent receives the notification in real time — no IMAP polling needed. The JSON payload includes message metadata (sender, subject, truncated message, timestamp) for downstream processing.<\/p>
How do I test whether my webhook is working?<\/h2>
Each webhook row has a Test button. Clicking it sends a sample POST to your URL so you can verify the endpoint receives and parses it — without sending a real email. Check the Recent deliveries table at the bottom for the result (timestamp, status, and response duration). If it fails, confirm your URL is reachable over public HTTPS and returns 200.<\/p>
How do I enable or disable a webhook without deleting it?<\/h2>
Use the Active toggle on the right side of each webhook row. Blue\/on = live and receiving events. Grey\/off = paused but configuration preserved. Useful during server maintenance or when deploying a new version of your endpoint.<\/p>
What does “Regenerate secret” do, and when should I use it?<\/h2>
Every webhook request includes a Bearer token in the Authorization<\/strong> header. Your endpoint can check this token to confirm the request came from Hostinger Mail.<\/p>
Regenerate token (from the ⋮ three-dot menu) creates a new token and immediately invalidates the old one. Use it when: the token may have been exposed, a team member with access has left, or you rotate tokens on a regular schedule.<\/p>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/05\/2026-05-19_09-27.png\")
<\/p>What are Allow\/Block lists and how do they affect my email?<\/h2>
Allow\/Block lists control outbound sending from each mailbox — they determine which addresses or domains the mailbox is permitted to send mail to.<\/p>
- \n
- Allow list<\/strong>: When non-empty, the mailbox can only send to addresses or domains on this list. Leave empty to allow sending to anyone.<\/li>\n
- Block list<\/strong>: Addresses or domains on this list are silently rejected at send time — they never receive the mail and the sender sees no bounce.<\/li>\n<\/ul>
You can add individual addresses (name@domain.com) or entire domains (domain.com) to either list. Lists are per-mailbox — use the dropdown at the top of the page to switch.<\/p>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/05\/2026-05-19_09-27_1.png\")
<\/p>What happens if an address is on both the Allow list and the Block list?<\/h2>
The Block list always takes priority. If an address (or its domain) appears on both lists, the email is silently rejected. This prevents a broad Allow entry (e.g. all of example.com) from accidentally overriding a specific block. You also can block entire domain e.g. example.com, but still allow peter@example.com.<\/p>
What can I do with the Agentic Mail REST API?<\/h2>
The Hostinger Mail REST API gives full programmatic control over your mailboxes. With a valid token your application can:<\/p>
- Block list<\/strong>: Addresses or domains on this list are silently rejected at send time — they never receive the mail and the sender sees no bounce.<\/li>\n<\/ul>
- Allow list<\/strong>: When non-empty, the mailbox can only send to addresses or domains on this list. Leave empty to allow sending to anyone.<\/li>\n
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/05\/2026-05-19_09-27_2.png\")
<\/p>![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/05\/2026-05-19_09-27_3.png\")
<\/p>