Skip to main content
Connic
Connectors

Custom Domains

Serve connector URLs from a hostname you own, with TLS handled for you.

Last updated
On this page

Hand partners and customers connector URLs on a hostname you own instead of connect.connic.co. The hostname uses a TLS certificate issued for your domain.

Default

https://connect.connic.co/webhook/3b0a9d…

Every project shares the same host.

Custom

https://hooks.acme.com/webhook/3b0a9d…

Your hostname, same connector underneath.

The connector keeps the same ID, configuration, and generated secrets. Only the host changes.

Available on Pro and up
Custom domains are included on Pro and Enterprise. If you downgrade to a plan without custom domains, requests to existing custom domains return 404 once the downgrade takes effect. Default connector URLs continue to work.

Adding a domain

Add domains in Project Settings → Domains. You'll need:

  • A subdomain you own. Apex domains and wildcards aren't supported. ASCII only; use punycode for IDNs.
  • DNS access to that subdomain. You'll add two records: a CNAME that routes traffic to Connic, and a TXT that proves ownership so a TLS certificate can be issued.

The domain becomes selectable after both DNS records resolve and its TLS certificate is active.

Using a domain on a connector

The Domain field applies to HTTP Webhook, MCP Server, S3, Stripe, Telegram, and WebSocket connector URLs. Pick an active domain in the create or edit dialog to use that host. The connector ID, configuration, and generated secrets stay the same.

  • The default URL stays live. Assigning a domain doesn't retire connect.connic.co. Both serve the same connector, so you can roll partners over one at a time.
  • Domains are project-scoped. One domain can serve connectors in any of the project's environments.

Removing a domain

Deleting a domain frees the hostname and automatically points any connectors that were using it back to the default host. Update third parties calling the old hostname first. They'll start getting 404s once the domain is gone.

Access control

Project permissions control who can view domains, add or remove them, and update connectors. Domain management and connector updates are recorded in the audit log.

Troubleshooting

Confirm the record exists at the exact name from the dashboard. dig TXT _acme-challenge.your.host should return the value Connic gave you. Some DNS providers strip the trailing label; paste the name as shown.

The CNAME must point to connect.connic.co. A flattened ALIAS or ANAME can work; an A record to an IP will not.

Usually the records appeared briefly and were then changed or removed. The row shows the underlying reason. Delete the domain and re-add the hostname to restart the flow.

The hostname routes correctly, but the path needs the connector's ID. Copy the full URL from the connector's detail drawer rather than constructing it by hand.

The domain remains pending until its DNS records resolve and its TLS certificate is active. Check the records from an external DNS resolver before troubleshooting further.

Explore connectors

Webhooks

The most common connector type to put a custom domain in front of.

Environments

One domain serves connectors across all environments in a project.

Connector Modes

Choose how external systems trigger your agents.

Private Networking

Connect agents to services on your private network.