Resources · Make integration

IONOS Make integrationAutomate IONOS with Make.

What if your DNS records followed your projects without a trip to IONOS? The IONOS Make integration gives you 7 modules to read, create, edit and remove DNS records and to list your domains. This guide is for anyone who runs sites on IONOS: connect your key, then build a first scenario.

Try the IONOS integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IONOS Make integration do for you?

The IONOS Make integration links your IONOS account to Make so a scenario (the automation you build in Make, a chain of steps) can handle your domains and DNS records for you. You get 7 modules, five actions and two searches, and no trigger: the scenario starts on a schedule or from another app.

A subdomain for every new client. A form or a spreadsheet row in another app starts the scenario, and Create a DNS record adds the entry under your domain without anyone opening the IONOS dashboard.

A clean switch to a new server. Search DNS records finds the entries of one domain, then Update a DNS record edits the one that must point somewhere else. Delete a DNS record removes an entry you no longer need.

An inventory you can share. List domains returns every domain of the account, and Get a DNS record reads one entry in detail, so you can copy both into a sheet your team reads.

Keep in mind that IONOS has no trigger in Make: nothing starts on its own when a record changes on the IONOS side. For anything the seven modules skip, Make an API call reaches the rest of the IONOS API with the same connection. If you weigh another tool, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans, and the Make troubleshooting guide helps when a run fails.

Connect

How do you connect IONOS to Make?

  1. 01

    Create an API key in IONOS

    In your IONOS dashboard, open the Developer API or API Access section and click Create New Key. Give the key a name, click Next, then copy both the public prefix and the secret shown on screen.

  2. 02

    Add an IONOS module in Make

    In your scenario, add any IONOS module and click Create a connection. A connection is your IONOS account linked to Make once, then reused by every IONOS module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the public prefix and the secret you copied from IONOS, or follow the instructions Make shows on screen, and confirm. Once the connection exists, Make can read your domains and fill the module fields for you.

First scenario

Your first scenario with IONOS

GoalWhen a new request arrives in another app, Make finds the matching DNS records in IONOS and updates the right one.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where requests land, a form or a sheet, since IONOS has no trigger of its own.

  2. 02

    Add Search DNS records

    Click the + on the right, search for IONOS and pick Search DNS records. Create the connection with your API key, then choose the domain from the list Make reads.

  3. 03

    Add Update a DNS record

    Add Update a DNS record after the search. Map (link a field to data from an earlier module) the record found by the search, then the new content from the request so each run edits the right entry.

  4. 04

    Test with Run once

    Click Run once and send one test request. Open each module to read the bundles it received, a bundle being one item passed along, here one DNS record.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Modules

What the IONOS modules do

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

IONOS1

Create a DNS record

ActionIn the docs only

Adds a new DNS entry to one of your domains straight from a scenario, so a subdomain or a verification record exists without a trip to the IONOS dashboard.

When to use it
a new client signs up and needs a subdomain under your agency domain, created as soon as the request is approved.
Watch out
check first with Search DNS records that the entry is not already there, or you may end up with two.
IONOS2

Delete a DNS record

ActionIn the docs only

Removes one DNS entry from a domain, which keeps your zone tidy once a project, a test site or an old service is gone.

When to use it
a client contract ends and the subdomain you created for them should disappear along with the account.
Watch out
a deletion cannot be undone from Make, so run the scenario once on a test domain and read the bundle before switching it on.
IONOS3

Get a DNS record

ActionIn the docs only

Reads a single DNS entry you already know, and hands its details to the next module so you can compare, log or reuse them.

When to use it
you stored a record in a sheet earlier and want to confirm what it holds today before a change goes out.
Watch out
it targets one known record; when you only know the domain, start with Search DNS records instead.
IONOS4

List domains

SearchIn the docs only

Returns the domains of your IONOS account, one bundle per domain, which gives your scenario a starting list to work through.

When to use it
you want an up to date inventory of every domain in a shared sheet, or you need to run the same check on each one.
Watch out
each domain becomes its own bundle, so every module placed after it runs once per domain and uses operations accordingly.
IONOS5

Make an API call

ActionIn the docs only

Opens the rest of the IONOS API to your scenario, with the connection you already set up, when none of the six other modules covers what you need.

When to use it
a step of your process exists in the IONOS API but has no module in Make, and you are comfortable reading the IONOS API documentation.
Watch out
this module expects you to build the request yourself, so keep the dedicated modules whenever one fits.
IONOS6

Search DNS records

SearchIn the docs only

Looks through the DNS records of a domain and hands back the entries that match, so later steps know exactly which record to touch.

When to use it
before an update or a deletion, to find the record behind a subdomain when you do not have its identifier at hand.
Watch out
a search can return zero, one or several records; plan for the empty case and for several matches before mapping the result.
IONOS7

Update a DNS record

ActionIn the docs only

Edits an existing DNS entry so it points where your project now lives, without recreating it and without logging in to IONOS.

When to use it
a site moves to a new host and its subdomain must follow, right after the move is confirmed in your tracking tool.
Watch out
map the record returned by Search DNS records rather than typing it by hand, or the scenario may edit the wrong entry.
Need help

Need help automating IONOS with Make?

A person reads every message.

FAQ

IONOS and Make: frequent questions

01Is the IONOS Make integration free?
Yes, IONOS is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run, and you still need your own IONOS account.
02What do you need to connect IONOS to Make?
You need an active IONOS account and an API key created in it. In the Developer API or API Access section of the dashboard, click Create New Key, name it, then copy the public prefix and the secret shown on screen. In Make, add any IONOS module, click Create a connection, give it a name if you like and paste both values. The same connection then serves all seven IONOS modules, including Make an API call.
03Does the IONOS Make integration react in real time?
No, because IONOS has no trigger in Make, so a change on the IONOS side does not start a scenario by itself. You start the flow another way: with a trigger from another app, such as a form or a sheet, or with the schedule set on the first module, every 15 minutes by default, which is also the shortest interval on the Free plan. The IONOS modules then run as the second and later steps of the scenario.
04What if the IONOS module you need is missing in Make?
It depends on the task. The seven modules cover domains and DNS records: create, read, search, update and delete records, plus list domains. For anything else the IONOS API offers, add Make an API call, which uses the same connection and can reach any endpoint of that API. The official documentation also warns that it was generated with AI from IONOS sources and may hold mistakes, so check important details with IONOS directly.
05Should you use Make or n8n for IONOS?
It depends on your criteria rather than on a winner. With Make, IONOS comes as seven ready modules plus Make an API call, and the scenario is built visually from a trigger of another app or a schedule. Before choosing, check whether the tool you consider offers the IONOS actions you need, how it would start the flow without an IONOS trigger, and which plan fits the number of scenarios you plan to keep active.
Same platform

Other docs you might need on this stack.

Browse all integrations