Hostinger Email
Send and read a Hostinger-hosted mailbox — SMTP for mail.send, IMAP for mail.fetch. The transport is prefilled — you only supply the mailbox and password.
Hostinger Email has no typed nodes of its own: it connects as a stored credential that 2 generic nodes use — the node picks Hostinger Email from the connection you select.
Before you connect Hostinger Email
- Authentication
- Username & password, Custom — any one of these.
- Credential
- {"client_id", "client_secret", "refresh_token"} or {"username", "password"}{"api_key"} or {"username", "password"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Hostinger Email
Operations of the generic nodes your Hostinger Email connection drives, grouped by what they do to your data.
Create and send 1
- Send Email
Read and search 1
- Fetch Email
Nodes that use your Hostinger Email connection
These generic nodes accept your Hostinger Email credential. Each chooses the provider from the connection you select, so the same node also works with the other providers shown.
- Fetch Emailmail.fetchRead the next matching message from a Gmail, Outlook or IMAP inbox.Also works withGmailOutlook / Microsoft 365
- Send Emailmail.sendSend an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.
A sample Hostinger Email workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Hostinger Email trigger is needed.
- 2Fetch Emailmail.fetchRead the next matching message from a Gmail, Outlook or IMAP inbox.
- 3Send Emailmail.sendSend an email through a SendGrid, SMTP, Hostinger, COAX Email API, Outlook or Gmail connection.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Hostinger Email questions
- How does OCNORA authenticate with Hostinger Email?
- With a stored Username & password or Custom credential, shaped {"client_id", "client_secret", "refresh_token"} or {"username", "password"} or {"api_key"} or {"username", "password"}. A connection test can check it when you add it.
- What can I automate with Hostinger Email?
- Hostinger Email has no typed nodes of its own. Your Hostinger Email connection is used by Fetch Email (mail.fetch), Send Email (mail.send).
- What if the Hostinger Email operation I need is not listed?
- Where Hostinger Email has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Hostinger Email?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Hostinger Email calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Hostinger Email workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.