Integration

Connect NetHunt CRM to Updown.io

When something happens in NetHunt CRM, your agent does the next thing in Updown.io. Describe it in plain language and the automation is built, tested on every branch and kept running.

NetHunt CRM8 triggersNetHunt CRM8 actionsUpdown.io10 actions

Browse all apps

Build it

What do you want NetHunt CRM and Updown.io to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with NetHunt CRM and Updown.io

Triggers and actions 8 triggers · 18 actions

Trigger
New Call Log
Triggered when a new call log is added to a record in the specified folder.
Trigger
New Comment
Triggered when a new comment is added to a record in the specified folder.
Trigger
New folder
Triggered when a new folder is added.
Trigger
New Google Drive File in Folder
Polls a NetHunt folder for newly attached Google Drive files linked to its records. Input: folder_id. Returns the list of new Google Drive file attachments.
Trigger
New or Updated Record in Folder
Triggered when a record is created or updated in the specified folder.
Trigger
New Record in Folder
Triggered when a record is created in the specified folder.
Trigger
Two-way sync new or updated records in folder
A trigger for two-way syncing new and updated records in a specified folder, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.
Trigger
Updated Record in Folder
Triggered when a record is updated in the specified folder.
Action
Add Call Log
Add a call log to the specified record.
Action
Add Comment
Add a comment to the specified record.
Action
Delete Record
Delete a record by ID.
Action
Find Record
Search records in a folder by ID or text query.
Action
Find record by field value
Finds one record in a NetHunt folder by matching a field value, and projects the record's fields map alongside record_id / id / created_at. DYNAMIC OUTPUT — DOCUMENTED EXCEPTION TO THE DESIGN RULE (2026-07-20). The standing rule puts FIND ops in the IDs-only bucket: GET enriches output with a field picker, FIND/LIST return IDs only. This op is a deliberate exception because NetHunt exposes NO get-by-id endpoint, so there is no GET op that could carry the picker. Re-confirmed against live data: ?query=<recordId> returns [] for a record that demonstrably exists in that folder (record 6a48901d931c9b3a9bbfb83c in Contacts), recordId:x 400s, and find-record-by-id 404s. The choice was therefore FIND-or-nothing, and a NetHunt user with no output picker has no way to map folder fields at all. If NetHunt ever ships a get-by-id endpoint, move the picker to a proper GET op and revert this op to IDs-only. Field values are projected under `fields`, a flat object keyed by field NAME, matching the house convention of a dynamic map beside the record's own top-level keys (cf. Agile/Cliniko/Capsule/MINDBODY `custom_fields`). NetHunt has no standard-vs-custom split — every folder field is user-defined — so the whole `fields` object is the dynamic surface and the container keeps the accurate name `fields` rather than `custom_fields`. The picker is parameterized per folder: `folder_id` is a SETTING (not an input) because dynamic-schema resolution binds only against step settings, so an input-sourced folder could never resolve the discovery at automation-load time. TYPE BLINDNESS (inherent, not fixable here): the backing schema endpoint returns only {name} with no type, so the picker advertises every field as String. Live reads return numbers and lists — e.g. Deal amount 100000 and Probability 0.9 are numbers, and Company / Contact person / Manager / Email / Label are ARRAYS (link fields carry record-id arrays). Mapping one of these as a scalar fails at runtime with no design-time signal.
Action
List Folder Fields
List the fields of a folder.
Action
List Readable Folders
List all folders the user can read.
Action
List Writable Folders
List folders the user can create records in.
Action
Create Check
Creates a new uptime check in updown.io for a URL you want monitored, and returns the created check including its token.
Action
Create Recipient
Adds a new alert recipient (email, SMS, webhook, Slack-compatible or Microsoft Teams) to your updown.io account and returns the created recipient.
Action
Delete Check
Deletes an uptime check from updown.io by its token.
Action
Delete Recipient
Removes an alert recipient from your updown.io account by its id.
Action
Get Check
Returns a single updown.io uptime check by its token, including its current status, uptime and settings.
Action
Get Check Metrics
Returns performance metrics for an updown.io check over a period — uptime, apdex, request counts and average timings, optionally grouped by time or monitoring location.
Action
List Checks
Returns every uptime check on your updown.io account with its current status and settings.
Action
List Downtimes
Returns the recorded outages for an updown.io check, newest first, with the reason, start and end times and duration of each.
Action
List Recipients
Returns every alert recipient on your updown.io account — email addresses, phone numbers, webhooks and chat integrations.
Action
Update Check
Updates the settings of an existing updown.io uptime check — its URL, name, interval, threshold, alert muting and more. Anything left blank keeps its current value.

Each app on its own

The other way round: Updown.io to NetHunt CRM