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, plus opted-in contacts from checkout
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
Each integration's card shows whether it's currently connected. If what you need isn't listed, Request integration passes the suggestion to the team.
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.
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, and segments, 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:
An API token, generated from the API tokens button on the Integrations page. 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.
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: August 26, 2026
Last updated
Was this helpful?
