InMotion Hosting

Run your site design, CMS content, hosting, CDN delivery, and SSL on Webflow while InMotion Hosting keeps your domain registration, DNS, and business email in place. A few record changes in cPanel are all it takes to connect the two.

Edit A, CNAME, and TXT records in InMotion's cPanel Zone Editor to route web traffic to Webflow's servers, and leave MX records pointed at InMotion for email. The two platforms operate on different layers of the stack, so they fit together without conflict.

How to integrate InMotion Hosting with Webflow

InMotion Hosting has provided web hosting since 2001 and has over 170,000 customers. It offers shared, VPS, dedicated, and reseller hosting plans, all managed through cPanel and WHM. InMotion also offers domain registration, email hosting (including Titan-based Professional Email), and developer tools like SSH access, Git integration, and multiple PHP/Python/Node.js runtimes.

Add three DNS records in InMotion's cPanel Zone Editor to connect your InMotion domain to Webflow. This is the most common integration path and requires no code. You need a paid Site plan and your domain's nameservers pointed to InMotion before DNS changes in cPanel take effect. Always copy DNS values from your own site settings, not from external tutorials, because the April 2025 Cloudflare infrastructure migration means values can differ between sites.

Many teams keep domain registration and email at InMotion while building the site in Webflow, with no need to move registrars or email providers. You can also run backend APIs on an InMotion VPS and call them from Webflow pages through custom code.

InMotion Hosting and Webflow connect in four ways:

• DNS domain connection lets you point an InMotion-registered domain to Webflow through cPanel record changes.
• Email hosting configuration keeps InMotion email running on the same domain your Webflow site uses.
• Code Embed elements let you embed InMotion-hosted forms, widgets, and scripts directly on Webflow pages.
• The Data API v2 and cPanel/WHM APIs can handle CMS content syncing, form routing, and some automation workflows, but they require server-side development. DNS automation generally requires WHM/root or reseller access on eligible InMotion environments.

Most implementations combine the DNS and email methods. If you have backend requirements, layer the API approach on top.

Point your InMotion domain to Webflow

Add three DNS records in InMotion's cPanel Zone Editor to connect your InMotion domain to Webflow. This is the most common integration path and requires no code. You need a paid Site plan and your domain's nameservers pointed to InMotion before DNS changes in cPanel take effect. Always copy DNS values from your own site settings, not from external tutorials, because the April 2025 Cloudflare infrastructure migration means values can differ between sites.

To connect your root domain:

1. Go to Site settings > Publishing > Production > Add a custom domain > Manually add domain. Enter your domain and note the three DNS records displayed: an A record, a CNAME record, and a TXT verification record.
2. Log into InMotion's cPanel. Go to Domains > Zone Editor and click Manage next to your domain.
3. Delete any existing A records on the @ hostname and any existing CNAME records on the www hostname. Keep MX records in place.
4. Click +Add Record and add the A record: Type = A, Hostname = @, Address = the IP from your site settings.
5. Add the CNAME record: Type = CNAME, Hostname = www, Target = cdn.webflow.com.
6. Add the TXT record: Type = TXT, Hostname = _webflow, Value = the full verification string shown in your site settings.
7. Back in Site settings, click Check status. Once verified, click Publish. SSL provisions automatically.

DNS propagation can take up to 48 hours, though most records resolve within a few hours. You can monitor propagation with a tool like whatsmydns.net. If your domain has CAA records in the DNS zone, add entries for both letsencrypt.org and pki.goog so SSL provisioning succeeds.

Route subdomains to InMotion or additional Webflow sites

After pointing @ and www to Webflow, you can route other subdomains separately. Point a subdomain like shop.yourdomain.com to your InMotion server, or send blog.yourdomain.com to a separate Webflow site.

To point a subdomain to InMotion:

1. In cPanel > Zone Editor > Manage, click +Add Record.
2. Select type A. Enter the subdomain prefix (e.g., shop) as the hostname and your InMotion server IP as the address.
3. Save the record.

Once saved, that subdomain resolves independently from your main Webflow site.

To point a subdomain to a second Webflow site:

1. Add a CNAME record with the subdomain prefix (e.g., blog) pointing to cdn.webflow.com.
2. Add a TXT record with hostname _webflow.blog and the verification string from the second site's settings.
3. In the second site, go to Site settings > Publishing > Production, add blog.yourdomain.com, verify, and publish.

After verification, you can publish the subdomain separately from your primary site.

Each subdomain pointing to a different Webflow site requires its own paid Site plan.

Set up InMotion email for your Webflow domain

Email routing stays with your MX records while your website points to Webflow through A and CNAME changes. InMotion's support documentation explicitly covers this scenario, describing how to keep email hosted at InMotion while pointing a domain's web traffic to another provider. In most cases, your existing InMotion email keeps working without any additional configuration.

Keep existing cPanel email

If you already use InMotion's cPanel email and you follow the DNS steps above, changing only A and CNAME records and leaving MX records alone, your email accounts continue to function. No additional steps are needed.

If your MX record points to mail.yourdomain.com, keep that subdomain's A record pointed to InMotion's mail server IP. Check InMotion's Zone Editor to confirm the mail A record is still directed at your InMotion cPanel IP, not at Webflow's IP.

Configure InMotion Professional Email (Titan)

InMotion's Professional Email product, powered by Titan, requires specific MX and SPF records. If you're setting up Titan email on a domain that points to Webflow, configure these records in InMotion's cPanel Zone Editor.

To set up Titan email records:

1. In cPanel > Zone Editor > Manage, remove any existing MX records and SPF TXT records for the domain.
2. Add two MX records: both with your domain as the hostname, one pointing to mx1.titan.email and the other to mx2.titan.email.
3. Add a TXT record for SPF: hostname = your domain, value = v=spf1 include:spf.titan.email ~all.

Titan now handles email while your Webflow site serves the same domain.

You can only have one SPF record per domain. If you already have an SPF record for another service, merge the values into a single record instead of creating a duplicate. InMotion's Professional Email setup guide covers the full configuration.

Embed InMotion-hosted content with Code Embed elements

When you need server-side functionality on a page, such as a PHP form, a widget, or a backend application, embed InMotion-hosted content using Code Embed elements. Code Embed supports HTML, CSS in <style> tags, and JavaScript in <script> tags. Server-side languages run on InMotion's server when you load the content through an iframe.

Embed an InMotion-hosted form via iframe

If you run a PHP contact form or application on your InMotion server, display it inside a page using an iframe in a Code Embed element.

To add the embed:

1. Open the page and add a Code Embed element from the elements panel.
2. Double-click the element to open the code editor.
3. Paste the iframe code pointing to your InMotion-hosted file:

<iframe
  src="https://yourdomain.com/your-inmotion-form.php"
  width="100%"
  height="500"
  frameborder="0"
  title="Contact Form">
</iframe>

4. Click Save & Close, preview the page, and publish.

JavaScript widgets, such as chat tools, booking systems, and analytics snippets, work the same way. Paste the provider's <script> tag directly into a Code Embed element on the page where you need it.

Add site-wide scripts via custom code settings

For scripts that should load on every page, go to Site settings > Custom Code and paste the snippet into the Custom code in head and body tags fields. You need a paid Site plan to publish custom code.

Build with the Data API and cPanel APIs

For programmatic integrations, connect InMotion-hosted backend services to Webflow through the Data API v2 and cPanel/WHM APIs on eligible InMotion environments. This path requires server-side development and fits teams that need automated CMS content syncing, form submission routing to external systems, or account-level and server-level automation. On eligible InMotion environments, use cPanel's UAPI for account-level operations and WHM API 1 for server-level operations when you have root or reseller/WHM access. DNS automation generally depends on WHM access rather than standard access on every plan.

Available APIs:

• The Data API v2 handles CMS collections, form submissions, site publishing, and webhook registration.
• The cPanel UAPI handles email account management, DNS lookups, and account-level operations.
• WHM API 1 handles DNS zone management, account provisioning, and server-level configuration (requires root or reseller access).
• Webhooks trigger real-time HTTP POST requests to your InMotion server when site events occur.

Together, these APIs support content and workflow automation across both platforms, and on qualifying environments they can also handle DNS changes.

Browser-side JavaScript on a published page cannot call the Data API directly because of CORS restrictions. Route all API calls through a server-side application on your InMotion VPS or dedicated server.

Sync CMS content from an InMotion backend

An application running on InMotion can write content into the CMS through the Data API. This is useful for syncing blog posts, product catalogs, or event listings from an InMotion-hosted database.

To create a CMS item from your InMotion server:

1. Generate an API token under Site settings > Apps & Integrations > API access. Select the cms:write scope.
2. Send a POST request to create a staged CMS item:

curl -X POST https://api.webflow.com/v2/collections/{collection_id}/items \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "isArchived": false,
    "isDraft": false,
    "fieldData": {
      "name": "My Article Title",
      "slug": "my-article-title"
    }
  }'

3. Publish the staged items to make them live:

curl -X POST https://api.webflow.com/v2/collections/{collection_id}/items/publish \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"itemIds": ["643fd856d66b6528195ee2ca"]}'

Bulk updates support up to 100 items per request. For read operations, use the Content Delivery API at api-cdn.webflow.com, which serves cached responses that don't count against your rate limit quota.

Route form submissions to an InMotion server

Webhooks can forward form submission data to an endpoint running on your InMotion server. Use this to handle form data with custom logic, store it in a database, or relay it to a CRM.

To set up form routing:

1. Register a webhook through the Data API:

curl -X POST https://api.webflow.com/v2/sites/{site_id}/webhooks \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "triggerType": "form_submission",
    "url": "https://your-inmotion-server.com/webhook-receiver"
  }'

2. On your InMotion server, create an endpoint that accepts POST requests with JSON payloads. The payload includes field values, the form name, and a submission timestamp.
3. Return HTTP 200 to acknowledge delivery. If your endpoint fails to respond, the webhook retries 3 times at 10-minute intervals.

Each request includes x-webflow-signature and x-webflow-timestamp headers for payload verification. If your InMotion server runs Apache, add CORS headers in .htaccess to accept requests from your domain, scoping Access-Control-Allow-Origin to your specific domain rather than *.

What can you build with the InMotion Hosting integration?

With InMotion Hosting connected to Webflow, you can run a full web presence — domain, email, and backend services — without moving away from InMotion infrastructure.

• Business site with branded email: Build your marketing site in Webflow while InMotion handles you@yourdomain.com email through cPanel or Titan Professional Email. DNS records split web traffic and email routing on the same domain with zero overlap.
• Hybrid SaaS architecture: Point www.yourdomain.com to your marketing site and app.yourdomain.com to an InMotion VPS running your application backend. Subdomain routing in cPanel's Zone Editor keeps both services on a single domain.
• Agency multi-client portfolio: Use InMotion's reseller hosting with WHM to manage domain registration, DNS, and email for dozens of client domains. Each client's site gets its DNS records pointed through InMotion, with isolated cPanel accounts for per-client email management.
• Content sync workflow: Run a content database on an InMotion VPS and sync entries into your CMS collections through the Data API. Product catalogs, event listings, or job boards stay current without manual entry.

If you need automated content syncing or real-time form processing, take the API integration path.