Hatz AI and Updown.io Integration
Automate the handoff between Hatz AI and Updown.io - your ai events flow into developer tools actions on a visual canvas your team can read. Set up the workflow once with 3 simple steps in the WEXTL® builder, let AI take smart decisions between apps, and never write a line of glue code again.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Hatz AI and Updown.io
Detailed info you need to know about Hatz AI and Updown.io integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Hatz AI to Updown.io
Set up your Hatz AI and Updown.io integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Hatz AI and Updown.io
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Hatz AI and Updown.io nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Hatz AI and Updown.io. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Hatz AI and Updown.io work in WEXTL?
WEXTL exposes actions and triggers for Hatz AI and Updown.io that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Updown.io triggersHatz AI actions
Updown.io modules
- Create a Check Starts monitoring a URL or a heartbeat with updown.io. Use Period (Seconds) to set how often it runs and Apdex Threshold to set the response time that counts as satisfying.
- Create a Recipient Adds a place to send alerts, such as an email address, a phone number for SMS, or a webhook URL. Use Select on All Checks to attach it to every check you already have.
- Create a Status Page Builds a page that shows the state of several Checks, in the order given. Use Visibility and Access Key to control who can open it.
- Delete a Check Deletes one monitoring check from updown.io. This cannot be undone.
- Delete a Recipient Removes an alert recipient from your updown.io account. A webhook recipient may belong to a workflow trigger.
- Delete a Status Page Removes a published status page. This cannot be undone.
- Get a Check Reads one check with its URL, Uptime, Period and current Down state. Turn on Include Metrics for the last hour of performance figures, or Include Results for the last 5 requests.
- Get Check Metrics Reads Uptime, Apdex, Timings and Requests for one check over a period. Use From and To to set the window and Group By to split the totals.
- List Check Downtimes Finds each outage of one check with its Started At, Ended At and Duration (Seconds). Turn on Include Results to add the requests before the downtime and after recovery.
- List Checks Lists every check in your updown.io account with its Token, URL, Alias and Uptime. Use Limit to return fewer rows when you only need a few.
- List Node IP Addresses Lists the IP Address values that updown.io sends its checks from, for firewall allow lists. Use Address Family to get only IPv4 or only IPv6.
- List Nodes Shows the monitoring locations of updown.io with their Code, City and Country. Each row also has IPv4 and IPv6 values for that node.
- List Recipients Gets the alert recipients on your account, each with its ID, Type, Name and Value. Run it to find the ID of a recipient before removing one.
- List Status Pages Retrieves your status pages, each with its Token, Name and Visibility. Checks on every page are included.
- Make an API Call Calls the Updown.io REST API directly with a free-form request under your saved credential.
- Update a Check Edits the URL, Period (Seconds), Apdex Threshold or Enabled setting of an existing check. Alias, String Match and Mute Until change only when filled in.
- Update a Status Page Renames a status page or edits its Description, Visibility and Access Key. Use Checks to replace the whole list of checks it shows.
- Watch Events Starts the workflow the moment updown.io reports a check going down or coming back up. Use the Event, Time and Description values of each alert, plus the Check Alias and Check URL.
Hatz AI modules
- Create a Chat Completion Sends a conversation to a Hatz AI Model and gets its reply, with a Role and Content for each of the Messages. Output includes the Choices, the Model and the Usage.
- List Apps Lists apps with Name, Description, Default Model and User Inputs. Use Search to match words in the apps, or Limit to stop after a given number.
- Make an API Call Sends a free-form request to the Hatz AI REST API, signed with your saved credential.
- Query the App Runs a Hatz AI app with Input Variables, the same values you would enter in the Hatz AI Platform. Output includes the User ID.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Hatz AI and Updown.io integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Hatz AI and Updown.io.
References
List of sources used to gather information about the Hatz AI and Updown.io integration.
- Hatz AI and Updown.io integration source code, module specs and credentials implementation.
- Our Hatz AI and Updown.io integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Hatz AI and Updown.io, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Hatz AI integration information
- Updown.io integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Hatz AI and Updown.io integration page documentation. Used sources, the role of AI, and how the team validates the result.

