Assign a Domain to a New Add-on
Overview
If our team set up your Heroku app’s domains for you, your dashboard shows an All domains page instead of the setup wizard. When you add another add-on for a new domain, you don’t need to wait for us: your AI agent can give the new add-on its domain and start setup right away.
This works on Heroku apps whose setup we manage. On any other app, open the new add-on from the Heroku dashboard and choose its domain in the setup wizard.
You need an AI agent connected to your account first. See Connect AI Agents to Your WAF (MCP).
Steps
-
Add the domain to your Heroku app. We only assign domains that are already custom domains on the app:
heroku domains:add app.example.com -a your-heroku-app -
Create the add-on on the same Heroku app, on the plan you use for these domains:
heroku addons:create expeditedwaf:<plan> -a your-heroku-app -
Open the new add-on once from your Heroku app’s Resources tab. This adds it to what your agent can reach. You’ll see “We’re setting this up for you”.
-
Ask your agent to assign the domain, for example: “Assign app.example.com to the new add-on on your-heroku-app.” Before anything changes, we check that the domain is on your Heroku app, that the site answers over HTTPS, and that its CAA records allow our certificate authority. If all three pass, the domain is assigned to the add-on and its SSL certificate is ordered. Asking again for the same domain only reports where its setup stands.
-
Add the validation CNAME. Shortly after the order, the certificate authority gives us a CNAME record that proves you control the domain. Ask your agent for it (or open All domains in your dashboard) and add it at your DNS provider. See Domain Verification CNAME Questions.
-
Switch DNS. Once the certificate is issued and installed, the domain shows as ready for its DNS switch, with its IP address. Remove the domain’s existing CNAME record, then add an A record pointing to that IP address. See DNS CNAME and A Records.
The assignment, with the name of the person whose agent made it, is recorded in the new domain’s Audit Log.
If the Agent Can’t Assign the Domain
- Not a custom domain on the Heroku app: run the
heroku domains:addcommand from step 1, then ask again. - The site didn’t respond over HTTPS: the site must already load on that domain. Check it in a browser, then ask again.
- CAA records: the domain’s CAA records don’t allow our certificate authority. See CAA Records and Certificate Renewal.
- No add-on without a domain: every add-on on the app already has a domain. Create one (step 2), open it once (step 3), then ask again.
Assigning a domain orders its certificate, so a domain can’t be moved to a different add-on afterwards without our help. If you assigned the wrong one, contact support.