Integrations
Connect Hostinger Reach to your website, online store, WordPress, AI assistants, and your own systems to sync contacts and enable ecommerce automations.
Integrations keep contacts flowing into Reach without manual work, and unlock the ecommerce automations that need to know about orders and carts.
Find them under Integrations.
Available integrations
AI Builder
Sync contacts from a Hostinger AI Builder site, and place forms on its pages
Hostinger Ecommerce
Purchase and abandoned-cart triggers, opted-in contacts from checkout, and store knowledge for AI — mention any product or discount code when creating emails or forms and Reach already knows its details, prices, and images
WordPress
Collect contacts from WordPress forms and plugins, and keep your site in sync
Hostinger Connector
Manage Reach by asking an AI assistant, over a single MCP connection
Reach public API
Build your own integration against contacts and segments
The AI Builder, Hostinger Ecommerce, and WordPress cards show Connected once they're linked.
Sites and stores
Connecting a site is what makes contact sync and ecommerce triggers work. Once connected, new signups arrive on their own and orders can start an automation.
Hostinger AI Builder sites come in two modes, and Reach connects to both. Manual mode (formerly Website Builder) is the drag-and-drop editor, so you connect the site and place forms yourself. Agentic mode (formerly Horizons) builds the site from a chat, so you ask its AI to connect Reach and add a form for you. Reach labels the two as AI Builder (Manual) and AI Builder (Agentic) wherever the choice matters.
Each workspace connects one site of each kind — a WordPress site, a Manual AI Builder site, and an Agentic AI Builder site — and one store. A store can belong to only one workspace; one already in use elsewhere shows Connected to another profile.
WordPress sites hosted outside Hostinger connect through Connect site from another provider: download the Hostinger Reach plugin, upload it in WordPress, and activate it.
For ecommerce automations on WordPress, the store side matters as well as the site: WooCommerce needs to be installed and active, with the Reach integration enabled inside it. Reach tells you in the automation editor when a trigger can't work because the store isn't ready, and links to where to fix it.
Note: Abandoned-cart timing comes from the store, not from Reach. See Automations.
Hostinger Connector
Hostinger Connector exposes Reach to AI assistants such as ChatGPT, Claude, and Cursor through the Model Context Protocol, so you can work in natural language instead of clicking through the app:
"Show me contacts added this week"
"Create a contact and tag it Webinar"
"Rename the segment Winter leads to Q1 leads"
"How many contacts do I have in total?"
It covers contacts, tags, segments, custom fields, and imports, and is included with your Hostinger plan.
Reach public API
The API suits custom setups and syncing from systems with no ready-made integration. Working with it takes three things:
A Hostinger API token, created from Generate API token on the Reach public API page (open it with Learn more). One token covers Reach and other Hostinger APIs.
Your profile ID, which identifies the workspace you're operating on.
The endpoints themselves — create and update contacts, and manage segments.
Pass the token as a bearer token in the Authorization header. Full reference documentation is linked from the API page, and the same endpoints work from workflow tools such as n8n if you'd rather not write code.
Treat tokens like passwords: store them in a secrets manager, never in source control, and revoke any that leak.
API tokens
API tokens, at the bottom of the Integrations page, manages tokens that connect this workspace to your own systems, such as the WordPress plugin. Give each token a name. It's shown only once, so copy it straight away. Deleting a token with Delete token breaks anything still using it immediately.
Related pages
Contacts — where synced contacts land
Automations — the flows that ecommerce triggers drive
Hostinger Connector — installing and using the Connector
API Reference — Hostinger's wider API and CLI
Last updated: September 25, 2026
Last updated
Was this helpful?