Connect NetHunt CRM to StatusCake

Both apps 35NetHunt CRM 16StatusCake 19

• 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.

• Trigger
  New Latest Page Speed Test

  Triggers when a new test is created, and provides basic pagespeed test data information.

• Trigger
  New Latest SSL Test

  Triggers when a new test is created, and provides basic ssl test data information.

• Action
  Add contact group

  Create a new contact group for alert notifications. POST /contact-groups

• Action
  Create Page Speed Test

  Creates a new pagespeed test for your StatusCake account.

• Action
  Create SSL Test

  Creates a new SSL test for your StatusCake account.

• Action
  Create Uptime Test

  Creates a new uptime test for your StatusCake account.

• Action
  Delete contact group

  Delete a contact group by id. DELETE /contact-groups/{id}

• Action
  Delete page speed test

  Delete a pagespeed check by id. DELETE /pagespeed/{id}

• Action
  Delete SSL test

  Delete an SSL check by id. DELETE /ssl/{id}

• Action
  Delete uptime test

  Delete an uptime check by id. DELETE /uptime/{id}

• Action
  Get contact group

  Retrieve a single contact group by id. GET /contact-groups/{id}

• Action
  Get page speed test

  Retrieve a single pagespeed check by id. GET /pagespeed/{id}

• Action
  Get SSL test

  Retrieve a single SSL check by id. GET /ssl/{id}

• Action
  Get uptime test

  Retrieve a single uptime check by id. GET /uptime/{id}

• Action
  List contact groups

  List all contact groups for the account. GET /contact-groups

• Action
  List SSL tests

  List all SSL checks for the account. GET /ssl

• Action
  Update contact group

  Update an existing contact group by id. PUT /contact-groups/{id}

• Action
  Update page speed test

  Update an existing pagespeed check by id. PUT /pagespeed/{id}

• Action
  Update uptime test

  Update an existing uptime check by id. PUT /uptime/{id}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.