IONOS
Developer ToolsManage IONOS DNS from agent workflows. Agents list zones, create, update, and delete records in bulk, and enable Dynamic DNS so routers and scripts keep A and AAAA records current through the IONOS Developer DNS API.
What This Integration Enables
DNS is the lowest-frequency, highest-consequence change surface in most operations. Weeks pass without touching it, then a migration or a customer onboarding demands twenty records in an afternoon, and a single typo takes down mail or the storefront. This connector puts IONOS DNS behind FlowRunner workflows: agents read zones, create and update records in bulk through the IONOS Developer DNS API, and stand up Dynamic DNS credentials for hardware on changing IPs. The reads and the routine writes run at machine speed. The changes that can black-hole production traffic wait for a [human-in-the-loop](/concepts/human-in-the-loop) approval. - Resolve zones and audit every record in them, filtered by name or type - Create A, AAAA, CNAME, MX, TXT, and other records in bulk in one call - Update record content, TTL, priority, and disabled state without touching name or type - Issue and revoke Dynamic DNS update credentials for routers and scripts
Without FlowRunner
With FlowRunner
Use Case Scenarios
Subdomain provisioning as part of onboarding
Every new customer environment needs its own hostname. When the provisioning flow completes, the agent calls List Zones for the parent domain, checks the requested name against Get Zone, and writes the A record and its verification TXT record with Create Records in a single call. The record ids land in the runbook, [UptimeRobot](/integrations/uptimerobot) gets a monitor on the new hostname, and the onboarding channel in [Slack](/integrations/slack) sees the confirmation. What used to be a ticket to the one person with portal access is a step in the flow.
A domain migration with a verified manifest
Moving a domain into IONOS means recreating its records exactly. The agent reads the source zone through [Cloudflare](/integrations/cloudflare), builds the full manifest of records to replicate, and posts it for review: every name, type, content value, and TTL, side by side with the source. An engineer approves the manifest, Create Records writes the whole set in one call, and Get Zone re-reads the result so the agent can diff what was written against what was planned. The nameserver switch happens only after the diff comes back clean.
Dynamic DNS for a fleet on changing IPs
Branch office routers and lab hardware sit on residential-grade connections where the IP changes without notice. The agent calls Create Dynamic DNS for each site's hostname, stores the returned update URL and bot credentials in the site's inventory row in [Google Sheets](/integrations/google-sheets), and hands the URL to the router's DynDNS client. When a site is decommissioned, the agent looks up that configuration's bulk id and, after a person confirms the site, calls Delete Dynamic DNS for that id alone, revoking exactly one credential and nothing else.
Human-in-Loop Highlight
Delete Dynamic DNS has a sharp edge: called without a bulk id, it disables every Dynamic DNS configuration in the account and revokes all of their update credentials at once. Every router quietly keeping an A record current goes dark on its next IP change, and the failures surface site by site over the following days. So no FlowRunner agent ever calls it bare. The agent resolves the specific bulk id, presents exactly which configuration and which hostnames will lose their credentials, and waits for a person to confirm the scope. Delete Record gets the same treatment: it is permanent, and a deleted MX record does not announce itself until the mail stops arriving.
Agent Capabilities
8 actionsDNS Zones
2- List Zones Lists every DNS zone in the IONOS account with its id, name, and type. The first call in any flow, since record operations are keyed on the zone id.
- Get Zone Retrieves a zone with its records, optionally filtered by record name suffix or type. The audit primitive: one call answers what currently resolves under a domain.
DNS Records
4- Create Records Creates one or more records in a zone in a single call, each with a fully qualified name, type, and content, plus optional TTL, priority, and disabled state. The bulk write that makes migrations and provisioning one step instead of twenty.
- Get Record Retrieves a single record by id with its content, TTL, priority, disabled state, and last change date. Used to verify state before and after a change.
- Update Record Updates a record's content, TTL, priority, or disabled state. Name and type are immutable, which is a useful guarantee: an update can repoint a record but never silently turn it into something else.
- Delete Record Permanently deletes a record from a zone. Cannot be undone, which is why deletion flows present the record's current content to a person first.
Dynamic DNS
2- Create Dynamic DNS Enables DynDNS for one or more fully qualified domain names and returns an update URL with Basic-auth bot credentials for a router or script to keep A and AAAA records current. The provisioning step for hardware without a stable IP.
- Delete Dynamic DNS Disables a DynDNS configuration by bulk id and revokes its update credentials. With no bulk id it disables every configuration in the account, so agents always pass an explicit id and always behind confirmation.
Frequently Asked Questions
What can FlowRunner do with IONOS?
FlowRunner agents can run List Zones, Get Zone, and Create Records in IONOS, plus 5 more actions.
Does connecting IONOS to FlowRunner require OAuth?
No. IONOS connects to FlowRunner with an API key, no OAuth flow required.
Can IONOS trigger a FlowRunner workflow automatically?
IONOS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with IONOS
$100 in credits. No card required. Connect in minutes.