Custom Domains in Zapier Interfaces

Using Zapier with a custom domain lets you publish Zapier Interfaces under your own branded URL instead of a default subdomain. This guide explains how to connect a custom domain, configure DNS records, verify ownership, and manage SSL so your Interfaces look professional and stay secure.

What you need before adding a custom domain in Zapier

Before you connect a custom domain to an interface, make sure you have a few key pieces in place. This preparation avoids most setup errors and DNS issues.

Zapier account and Interfaces access

To manage domains for interfaces, you need:

An active Zapier account.
Access to Zapier Interfaces in your workspace.
Permission to edit the specific interface you want to publish.

Domain registrar and DNS access

You must be able to edit DNS records where your domain is hosted. This is usually your domain registrar or DNS provider. Common providers include:

GoDaddy
Cloudflare
Namecheap
Google Domains (or a similar DNS service)

Ask your administrator for access if you do not manage DNS directly.

Supported domain types for Zapier Interfaces

Zapier Interfaces supports using a custom domain (for example, example.com) or a subdomain (for example, forms.example.com). You can:

Point a subdomain to an interface for use as a landing page, portal, or form.
Use a dedicated subdomain just for Zapier Interfaces to keep your DNS organized.

How to add a custom domain in Zapier Interfaces

The process to connect a domain to Zapier Interfaces involves three main phases: adding the domain in the product, updating DNS records, and verifying ownership.

Step 1: Add the domain inside Zapier Interfaces

Sign in to your Zapier account.
Open the Interfaces section from your Zapier dashboard.
Select the interface you want to publish to a custom domain.
Go to the interface’s Settings or Publish area, where domain options are available.
Find the custom domain settings and click the option to Add domain or Connect custom domain.
Enter the domain or subdomain you want to use, such as portal.example.com.
Confirm to create the domain configuration.

Zapier will generate DNS records that you must add at your DNS provider. Keep this screen open while you update DNS so you can copy the exact values.

Step 2: Add DNS records at your domain host

Once you have the DNS details from Zapier, switch to your DNS provider’s dashboard to create the required records.

Log in to your domain registrar or DNS provider.
Open the DNS management area for your chosen domain.
Create the DNS records shown in the Zapier Interfaces domain setup screen. Typically, these include:

CNAME records pointing your subdomain (for example, forms) to a value provided by Zapier.
In some setups, an TXT record may be required for domain ownership verification.

When adding CNAME records:

Set the Name or Host to the subdomain you chose in Zapier Interfaces.
Set the Value or Target exactly as shown on the Zapier configuration page.
Save the DNS changes.

DNS propagation can take time. In many cases, changes appear within minutes, but it can take up to 24–48 hours depending on your TTL settings and DNS provider.

Step 3: Verify domain connection in Zapier

After the DNS records have been created, return to Zapier Interfaces to complete verification.

Go back to the domain settings for your interface in Zapier.
Click the option to Verify or Check DNS for your domain.
Wait while Zapier confirms that the required CNAME and TXT records are correctly configured.

If verification succeeds, your interface will be linked to the custom domain, and Zapier will start handling traffic for that host. If verification fails, double-check the DNS record names and values to ensure they match the instructions from Zapier Interfaces exactly.

SSL and security for custom domains in Zapier

When you connect a custom domain, Zapier manages SSL certificates for you. This means visitors can access your interface via HTTPS without needing to purchase or install your own certificate.

How SSL works with Zapier Interfaces

Zapier automatically provisions an SSL certificate after your domain is verified.
The certificate is renewed by Zapier, so you do not have to track expiration dates.
Users will see a secure connection (HTTPS) in their browser when visiting your interface.

Because SSL setup is automated, your main responsibility is ensuring DNS records stay active and unchanged once they are working. Editing or deleting the required CNAME records can disrupt HTTPS access to your interface.

Managing and editing domains in Zapier Interfaces

After your custom domain is active, you can change which interface uses it, update settings, or remove it completely when no longer needed.

Change or update the interface connected to a domain

Within Zapier Interfaces, you can reassign a connected custom domain to a different interface:

Open Interfaces in your Zapier workspace.
Go to the Domains or Publishing section, depending on your interface layout.
Select the active domain from the list.
Use the available options to point the domain to another interface or environment (such as a production or test version).

You usually do not need to change DNS records when you just reassign the domain to another interface inside Zapier. The CNAME entries at your DNS provider can stay the same.

Remove or disconnect a custom domain from Zapier

If you no longer want to use a particular domain for Zapier Interfaces:

Open the domain management area in Zapier Interfaces.
Select the domain you want to disconnect.
Choose the option to Remove or Disconnect the domain.
Confirm the action.

After removal, visitors will no longer be able to access that interface through the custom domain. You can then delete the CNAME and TXT records from your DNS provider if they are not needed for anything else.

Troubleshooting domain issues in Zapier

Most custom domain issues result from incorrect or incomplete DNS settings. Use the following checks if your domain does not work as expected with Zapier Interfaces.

Verification still pending

If Zapier shows your domain as pending verification:

Verify that the CNAME record host matches the subdomain you entered in Zapier.
Make sure you did not accidentally create an A record instead of a CNAME.
Confirm that there is no conflicting record for the same host name.
Allow more time for DNS to propagate, especially if your TTL is high.

Domain returns an error in the browser

If your browser shows an error when you visit the custom domain:

Check that the domain status in Zapier Interfaces is active and verified.
Make sure your interface is published and not in a draft-only state.
Ensure the DNS CNAME records still exist at your DNS provider.

SSL or HTTPS warnings

When a new domain is added, SSL provisioning may take a short time:

Wait a few minutes after verification for the secure certificate to be ready.
Check again in Zapier to confirm that the domain shows as secure.
Do not add separate, conflicting SSL settings at your DNS provider or CDN.

Learn more about Zapier Interfaces and custom domains

For the full reference straight from the platform, you can read Zapier’s official documentation on how to add a custom domain to Interfaces at this support article. It provides up-to-date details on supported DNS configurations and interface publishing behavior.

If you want strategic help configuring complex setups, optimizing automation flows, or planning multi-domain structures, you can also review the resources at Consultevo for broader automation and integration guidance.

Once your custom domain is successfully connected to Zapier Interfaces, your users will enjoy a consistent, branded experience on a secure URL, while you retain full control over your automations and interface design.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.

Get Zapier Help