Resources · Make integration

GoDaddy Make integrationAutomate GoDaddy with Make.

Your domains and DNS records can be handled from a Make scenario instead of the GoDaddy dashboard. The GoDaddy Make integration gives you 7 actions and 3 searches. This guide shows how to link your API key, what each module does, and how to build a first scenario.

Try the GoDaddy integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GoDaddy Make integration do?

The GoDaddy Make integration lets a Make scenario (the automation you build, a chain of steps) read and change your GoDaddy domains and DNS records. It relies on an API key and secret from your GoDaddy account, and it covers purchase, renewal, domain details and DNS in 10 modules.

A DNS check without logging in. A web agency receives a support request about a client site. Search DNS Records lists the records of that domain, so whoever handles the ticket sees the current setup straight away. Get a Domain adds the details GoDaddy holds about the domain itself.

A name shortlist for a new project. A marketing team logs a product idea in a spreadsheet. Search Domains for Suggestions returns alternate names built from a seed domain or a set of keywords, ready to review before anyone buys.

DNS changes that follow a checklist. An IT lead who moves a site to a new host can drive the switch from a scenario: Update DNS Records replaces the records, Delete DNS Records removes the ones of a given type and name.

Keep one limit in mind: the Make documentation for GoDaddy is flagged as AI-generated from GoDaddy's own docs, so verify anything critical before you rely on it. The app has no trigger, so a scenario starts on a schedule or from another app. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing page shows how each plan counts operations.

Connect

How do you connect GoDaddy to Make?

  1. 01

    Create an API key in GoDaddy

    Open the GoDaddy developer portal dashboard and click Keys or API Keys in the main menu. Create a new key, pick the environment in the Environment dropdown, then copy both the API key and the API secret shown on screen.

  2. 02

    Add a GoDaddy module to your scenario

    In Make, add any GoDaddy module and click Create a connection. A connection is your GoDaddy account linked to Make once, then reused by every GoDaddy module. The Connection name field is optional but helps when you manage several accounts.

  3. 03

    Paste the credentials and save

    Enter the key and the secret you copied, or follow the instructions Make shows on screen. Once the connection is saved, the module fields open and you can start filling them.

First scenario

Your first scenario with GoDaddy

GoalWhen a support ticket names a client domain, Make lists the DNS records of that domain from GoDaddy.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Since GoDaddy has no trigger, pick the module of the app where tickets arrive.

  2. 02

    Add Search DNS Records

    Click the + on the right of the first module, search GoDaddy and choose Search DNS Records. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the domain

    In the GoDaddy module, map the domain name that comes from the ticket. Each bundle (one item passed from one module to the next) that reaches GoDaddy then carries the right domain.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the output of Search DNS Records and read the bundles: one per DNS record returned for the domain.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run counts as an operation, the unit Make bills on your plan.

Modules

The 10 GoDaddy modules in Make

GoDaddy gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

GoDaddy1

Create a Domain

Action

In Make“Purchases and registers the specified domain.”

This module buys and registers a domain on your GoDaddy account, so a new name can be secured as part of a launch workflow rather than through the checkout.

When to use it
after a project is approved and the chosen name has passed a check with Search Domains for Suggestions.
Watch out
it is a real purchase, so add a filter or an approval step before it and run it once on a name you actually want.
GoDaddy2

Delete DNS Records

Action

In Make“Deletes all DNS records for the specified domain with the specified type and name.”

Removes every DNS record of a domain that matches the type and the name you give, which clears out old entries left behind after a hosting move.

When to use it
when a service is retired and its records must disappear, instead of editing the full zone with Update DNS Records.
Watch out
all matching records go at once and nothing brings them back, so list them first with Search DNS Records.
GoDaddy3

Get a Domain

Action

In Make“Gets details for the specified domain.”

Returns the details GoDaddy stores for one domain you name, giving the next modules a single bundle to work with.

When to use it
when you already know the exact domain, for example the one typed in a client form, and want its data before deciding to renew or update it.
Watch out
it needs the precise name; to browse the domains of your account, start with Search Domains instead.
GoDaddy4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends an authorized request to any endpoint of the GoDaddy API while reusing the connection you already created, so you reach what the other nine modules leave out.

When to use it
when the operation you need has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the GoDaddy API documentation open and test with Run once before switching the scenario on.
GoDaddy5

Renew a Domain

Action

In Make“Renews the specified domain.”

Renews a domain you own, which keeps a client or brand name active without a manual stop in the GoDaddy dashboard.

When to use it
in a scenario that reads a domain with Get a Domain and renews only the names someone has confirmed are still needed.
Watch out
a renewal acts on a live domain, so place a filter in front of this module and never leave it running on every domain returned by a search.
GoDaddy6

Update a Domain

Action

In Make“Updates details for the specified domain.”

Changes the details of an existing domain on your account, so an administrative edit can follow an event in another tool rather than waiting for a login.

When to use it
when a domain changes hands inside your company and its settings must follow, after reading the current values with Get a Domain.
Watch out
this module touches the domain itself, not its DNS; for records, pick Update DNS Records.
GoDaddy7

Update DNS Records

Action

In Make“Replaces all DNS records for the specified domain.”

Replaces the whole set of DNS records of a domain with the set you send, which suits a planned switch to a new host or a new mail provider.

When to use it
when the target configuration is complete and written down, for instance in a migration sheet your team fills in.
Watch out
any record missing from what you send is gone afterwards, so pull the current list with Search DNS Records and include what must stay.
GoDaddy8

Search DNS Records

Search

In Make“Retrieves a list of DNS records for the specified domain.”

Lists the DNS records of a domain and hands each one to the next module as its own bundle, which gives you a snapshot of the zone without opening GoDaddy.

When to use it
before any change with Update DNS Records or Delete DNS Records, or to answer a support request about a site.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle.
GoDaddy9

Search Domains

Search

In Make“Searches for domains by given criteria.”

Searches domains by the criteria you set and returns them one bundle at a time, so a scenario can work through a list of names.

When to use it
to review many names at once, for example to feed a spreadsheet of client domains or to pick the ones a later module should read.
Watch out
each domain found adds operations to the modules after it, so narrow the criteria before a large run.
GoDaddy10

Search Domains for Suggestions

Search

In Make“Searches for alternate domain names based on a seed domain, a set of keywords, or the shopper's purchase history.”

Proposes alternate domain names from a seed domain, a set of keywords or the shopper's purchase history, which turns a rough idea into a list of candidates.

When to use it
at the naming stage of a product or campaign, when the obvious name is taken and the team needs options to compare.
Watch out
it only suggests names; buying one is a separate step with Create a Domain.
Need help

Need help automating GoDaddy with Make?

A person reads every message.

FAQ

GoDaddy Make integration: common questions

01Is the GoDaddy Make integration free?
Yes, on the Make side. GoDaddy is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need an active GoDaddy account, and Create a Domain makes a real purchase on that account.
02What do you need to connect GoDaddy to Make?
You need an active GoDaddy account and an API key with its secret. Create them in the GoDaddy developer portal dashboard under Keys or API Keys, choose the environment in the Environment dropdown, then copy both values. In Make, click Create a connection on any GoDaddy module, give it a name if you like, and paste the key and the secret. The same connection then serves all 10 modules, so you only do this once.
03Can GoDaddy start a Make scenario on its own?
No. The GoDaddy app in Make has no trigger, neither scheduled nor instant, so nothing in GoDaddy starts a scenario. You have two ways around it. Put a GoDaddy module first and let Make run it on a schedule, every 15 minutes by default on a new scenario. Or open the scenario with a trigger from another app, such as a form or a helpdesk, and place the GoDaddy modules after it.
04What if a GoDaddy module is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the GoDaddy API with the connection you already have, so you are not limited to the 7 actions and 3 searches. Write the request from the GoDaddy API documentation and test it with Run once. Keep in mind that the Make documentation page for GoDaddy is marked as AI-generated from GoDaddy's docs, so check critical details against GoDaddy itself.
05Should you use Make or n8n for GoDaddy?
It depends on the criteria that matter to your team, not on a winner. Make offers 10 GoDaddy modules plus Make an API Call, a visual editor and a Free plan to test on. Apps covered by Make often have an n8n node too, so check whether the node you need exists there before comparing. Then weigh how each tool counts usage, how your team prefers to build, and which other apps the workflow has to reach.
Same platform

Other docs you might need on this stack.

Browse all integrations