Connect NetHunt CRM to PagerDuty

Both apps 44NetHunt CRM 16PagerDuty 28

• 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
  List Maintenance Windows

  Gets a list of maintenance windows (GET /maintenance_windows).

• Trigger
  New Incidents

  Polls for new incidents in PagerDuty (GET /incidents, newest first).

• Action
  Add Responders

  Request additional responders (a user or escalation policy) to help with an incident.

• Action
  Add Team Member

  Add a user to a team with a given role.

• Action
  Create Incident

  Creates an incident in PagerDuty (POST /incidents).

• Action
  Create Note on Incident

  Creates a note on a given incident.

• Action
  Delete or End a Maintenance Window

  Deletes a maintenance window that hasn't started yet, or ends one that is ongoing.

• Action
  Get Escalation Policy

  Retrieve a single escalation policy by its ID.

• Action
  Get Incident

  Retrieve a single PagerDuty incident by id.

• Action
  Get Schedule

  Retrieve a single on-call schedule by its ID.

• Action
  Get Service

  Retrieve a single PagerDuty service by id.

• Action
  Get Team

  Retrieve a single team by its ID.

• Action
  Get User Information

  Gets a user's information based on provided ID.

• Action
  List Escalation Policies

  List PagerDuty escalation policies (GET /escalation_policies).

• Action
  List Incident Notes

  List all notes attached to an incident.

• Action
  List Incidents

  List PagerDuty incidents with filters (statuses, service_ids, urgencies, date range) (GET /incidents).

• Action
  List On-Calls

  List current on-call entries — who is on call now, by escalation policy/schedule/user/time window (GET /oncalls).

• Action
  List Schedule Overrides

  List overrides on a schedule within a required since/until time window.

• Action
  List Schedules

  List PagerDuty on-call schedules (GET /schedules).

• Action
  List Services

  List PagerDuty services (GET /services).

• Action
  List Teams

  List all teams in the account.

• Action
  List Users

  List PagerDuty users (GET /users).

• Action
  Manage Incidents

  Bulk acknowledge or resolve multiple incidents in a single call.

• Action
  Snooze Incident

  Snooze a triggered/acknowledged incident for a number of seconds so it won't re-alert until the snooze expires.

• Action
  Two-way sync add a maintenance window

  Creates a maintenance window for use with two-way sync triggers (POST /maintenance_windows). Does not update. Use only with two-way sync triggers.

• Action
  Two-way sync add or update an incident

  Creates or updates an incident for use with two-way sync triggers (POST /incidents; incident_key dedups). Use only with two-way sync triggers.

• Action
  Update Incident

  Updates an incident in PagerDuty. Set status to acknowledged or resolved to manage the incident.

• Action
  Update Maintenance Window

  Updates a maintenance window.

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