Hostinger Email
Connect Hostinger Mail for individual email and Hostinger Reach for audience preparation.
Oblive ships two separate Hostinger connectors because they serve different workflows:
| Connector | Use It For |
|---|---|
| Hostinger Mail | Reading, searching, organizing, replying to, and sending email |
| Hostinger Reach | Contacts, contact groups, segments, profiles, and domain readiness |
Hostinger Reach does not currently expose campaign drafting, scheduling, sending, or analytics through MCP. Use Hostinger Mail for individual messages; manage campaign operations in Hostinger Reach until its MCP surface supports them.
Connect
- Open Integrations and choose Hostinger Mail or Hostinger Reach.
- Choose read-only or full access.
- Select Continue to Hostinger and authorize the requested account.
- Review the enabled tools and confirm the integration reports ready.
Choose read-only access for mailbox or audience research. Full access permits reviewed sends and changes through the organization’s action policy. Chat remains read-only; consequential operations require a Growth or Support task.
Individual Email
Hostinger Mail can list and search messages, read message text and attachments, inspect folders and quota, manage folders and flags, send individual messages, and manage webhooks. Replies and forwards use the source message’s folder and UID so the provider can preserve thread references.
Every send is one durable external action. If provider state is uncertain after dispatch, Oblive does not retry it. Check Hostinger and reconcile the Human Inbox item instead.
Private Attachments
Task runs with full Hostinger Mail access receive a scoped attachment companion. It accepts up to 10
regular workspace files and 25 MiB in aggregate. The worker uploads each file to an exact private
object key; the backend verifies ownership, size, content type, and SHA-256, then base64-encodes the
bytes only for the approved sendEmail call.
Attachment bytes, local paths, OAuth credentials, and private object URLs never enter the durable action record. The approval preview shows recipients, subject, body, and bounded attachment metadata. Successful and rejected actions remove their staged files; uncertain sends retain them until human reconciliation. Configure a 24-hour lifecycle for abandoned integration staging objects.
Provider acceptance confirms that Hostinger accepted the request. It does not prove recipient delivery, inbox placement, or reading.