Integrations
Connect your cloud, DNS, domain and certificate providers, and alert destinations.
18 articles · 9 topics
Providers
Connect cloud, DNS, domain and certificate providers.
See all articles →7 articles · 5 topics
Alert destinations
Send alerts to Slack, Microsoft Teams, Telegram or Discord.
See all articles →2 articles
GitHub
Connect GitHub and use its events and actions in your automations.
See all articles →4 articles
Calendar
Put renewals, expiries and maintenance in the calendar you already use.
See all articles →4 articles · 3 topics
Automation
Connect Zapier, Make, n8n and your own tools in both directions.
See all articles →Articles
About integrationsIntegrations connect your provider accounts — like Hetzner, Cloudflare or AWS — to InfraNest, so your servers, domains, DNS and certificates all appear in…Create a GoDaddy access tokenTo connect GoDaddy, InfraNest needs a personal access token from the GoDaddy Developer portal.Connect GoDaddyConnect GoDaddy to manage your domains and DNS from InfraNest.Create a Namecheap API keyTo connect Namecheap, InfraNest needs API access turned on, your API credentials, and InfraNest's IP address approved.Connect NamecheapConnect Namecheap so you can manage your domains, DNS and SSL certificates from InfraNest.Create an IONOS API keyTo connect IONOS, InfraNest needs an API key. The same key covers DNS, domains and certificates.Connect IONOSConnect IONOS to manage your DNS, domains and SSL certificates from InfraNest.Create a Hetzner API tokenTo connect Hetzner, InfraNest needs an API token from your Hetzner project. The same token covers your cloud resources and your DNS zones.Connect HetznerConnect Hetzner so you can manage your cloud servers, DNS and SSL certificates from InfraNest.Create a TransIP API keyTo connect TransIP, InfraNest needs your account name and an API key (a private key).Connect TransIPConnect TransIP to manage your VPS servers, DNS, domains and SSL certificates from InfraNest.Connect Amazon Web Services (AWS)Connect AWS to manage your Route 53 DNS, Route 53 domains and ACM certificates from InfraNest.Set up AWS accessTo connect AWS, InfraNest needs access to your Route 53, Route 53 Domains and ACM. You can grant it with an IAM role (recommended) or with access keys.Get your SSL.com API keysTo connect SSL.com, InfraNest needs your API credentials.Connect SSL.comConnect SSL.com to bring your SSL certificates into InfraNest's certificate list, so they're tracked alongside everything else.Connect CloudflareConnect Cloudflare to manage your DNS, domains and SSL certificates from InfraNest. Your Cloudflare zones and records appear automatically once it's connected.Create a Cloudflare API tokenTo connect Cloudflare, InfraNest needs an API token from your Cloudflare account. Here's how to create one with the right permissions.Create a Dynadot API keyInfraNest talks to Dynadot with an API key and a signing secret. Here's how to create them.Connect DynadotConnect Dynadot to manage the domains you have registered there from InfraNest — renewals, nameservers, transfer lock, WHOIS privacy and contacts — and to…Connect SlackSend InfraNest alerts straight into a Slack channel, so your team sees incidents, expiries and status changes where they already work.Connect TelegramGet InfraNest alerts as Telegram messages — great for on-call, on your phone, wherever you are.Connect Microsoft TeamsDeliver InfraNest alerts into a Microsoft Teams channel, so incidents and expiries reach the whole team.Connect DiscordPost InfraNest alerts into a Discord channel — handy for communities and teams that live in Discord.Automate with PagerDutyPage your on-call for anything — not just a monitor going down — and react in InfraNest when responders act in PagerDuty.Set up PagerDuty two-way syncPaging PagerDuty works with just a routing key. This optional, one-time step adds the reverse direction: when someone acknowledges or resolves an incident in…Connect PagerDutyPage your on-call team through PagerDuty when a monitor goes down. When the monitor recovers, InfraNest resolves the PagerDuty incident automatically — and…Automate with GitHubBuild rules that react to GitHub activity and act back on GitHub — no scripts, no glue code.Connect GitHubLink GitHub to InfraNest so your automations can react to what happens in your repositories — and act back on GitHub for you.Subscribe with a calendar feed (iCal)Subscribe to a private link and your renewals, certificate expiries and maintenance windows appear in any calendar app — Google Calendar, Outlook, Apple…About calendar syncPut your renewals, expiries and maintenance windows in the calendar you already use, so a domain never lapses because nobody was looking at InfraNest that week.Connect Google CalendarConnect Google Calendar and your domain renewals, certificate expiries and maintenance windows appear in a dedicated InfraNest calendar that updates itself.Connect Outlook CalendarConnect Outlook Calendar — Microsoft 365 or Outlook.com — and your renewals, certificate expiries and maintenance windows appear in a dedicated InfraNest…Incoming endpoints and outgoing webhooksTwo things point in opposite directions, and knowing which one you need saves a lot of guessing.Connect ZapierStart a Zap when a domain is expiring, a monitor goes down or a certificate is about to lapse — and let a Zap open a maintenance window, pause a monitor or…Connect MakeStart a Make scenario when a domain is expiring, a monitor goes down or a certificate is about to lapse — and let a scenario open a maintenance window, pause…Connect n8nStart an n8n workflow when a domain is expiring, a monitor goes down or a certificate is about to lapse — and let a workflow open a maintenance window, pause…