Connect NetHunt CRM to JIRA

Both apps 154NetHunt CRM 16JIRA 138

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

  Polls for newly created issues in a project (ordered by creation date).

• Trigger
  New or Updated Issue

  Polls for issues created or updated recently (ordered by updated date).

• Action
  Add attachment

  add an attachment to an issue

• Action
  Add comment

  add a comment to an issue

• Action
  Add Comment to Issue

  Adds a comment to the specified issue.

• Action
  Add filter as favorite

  Add filter as favorite

• Action
  Add gadget to dashboard

  Add gadget to dashboard

• Action
  Add user to group

  add a user to a group

• Action
  Add vote

  add the current user's vote to an issue

• Action
  Add worklog

  add a worklog to an issue

• Action
  Archive issues by ID or key

  archive issues by ID/key

• Action
  Archive issue(s) by JQL

  Archive issue(s) by JQL

• Action
  Assign Issue

  Assigns an issue to a user by account ID.

• Action
  Bulk create issue

  bulk create issues

• Action
  Bulk create statuses

  Bulk create statuses

• Action
  Bulk delete issues

  bulk delete issues

• Action
  Bulk delete Statuses

  Bulk delete Statuses

• Action
  Bulk delete worklogs

  bulk delete worklogs on an issue

• Action
  Bulk edit dashboards

  Bulk edit dashboards

• Action
  Bulk edit issues

  bulk edit issue fields

• Action
  Bulk fetch issues

  bulk fetch issues by ID/key

• Action
  Bulk move issues

  bulk move issues

• Action
  Bulk move worklogs

  bulk move worklogs

• Action
  Bulk transition issue statuses

  bulk transition issue statuses

• Action
  Bulk unwatch issues

  bulk unwatch issues

• Action
  Bulk watch issues

  bulk watch issues

• Action
  Change filter owner

  Change filter owner

• Action
  Copy dashboard

  Copy dashboard

• Action
  Create component

  Create component

• Action
  Create custom field

  Create custom field

• Action
  Create dashboard

  Create dashboard

• Action
  Create filter

  Create filter

• Action
  Create group

  Create group

• Action
  Create Issue

  Creates a new issue in the specified project.

• Action
  Create issue link

  create a link between two issues

• Action
  Create issue link type

  create an issue link type

• Action
  Create issue type

  create an issue type

• Action
  Create project

  create a project

• Action
  Create project category

  create a project category

• Action
  Create related work

  Create related work

• Action
  Create user

  create a user

• Action
  Create version

  Create version

• Action
  Delete and replace version

  Delete and replace version

• Action
  Delete attachment

  delete an attachment

• Action
  Delete comment

  delete a comment

• Action
  Delete component

  Delete component

• Action
  Delete custom field

  Delete custom field

• Action
  Delete dashboard

  Delete dashboard

• Action
  Delete filter

  Delete filter

• Action
  Delete Issue

  Deletes an issue by its key or ID.

• Action
  Delete issue link

  delete an issue link

• Action
  Delete issue link type

  delete an issue link type

• Action
  Delete issue type

  delete an issue type

• Action
  Delete project

  delete a project

• Action
  Delete project asynchronously

  delete a project asynchronously

• Action
  Delete project category

  delete a project category

• Action
  Delete related work

  Delete related work

• Action
  Delete user

  delete a user

• Action
  Delete version

  Delete version

• Action
  Delete vote

  remove the current user's vote from an issue

• Action
  Delete watcher

  remove a watcher from an issue

• Action
  Delete worklog

  delete a worklog

• Action
  Export Archived Issues

  Export archived issue(s)

• Action
  Get all dashboards

  Get all dashboards

• Action
  Get all projects

  Get all projects

• Action
  Get attachment content

  get attachment content

• Action
  Get attachment metadata

  get attachment metadata

• Action
  Get available transitions

  Get available transitions

• Action
  Get bulk available transitions

  get transitions available for bulk transition

• Action
  Get comment

  get a single comment

• Action
  Get comments by IDs

  get comments by IDs

• Action
  Get component

  Get component

• Action
  Get create issue metadata

  Get create issue metadata

• Action
  Get create metadata issue types for a project

  get create-metadata issue types for a project

• Action
  Get dashboard

  Get dashboard

• Action
  Get edit issue metadata

  get edit metadata for an issue

• Action
  Get favorite filters

  Get favorite filters

• Action
  Get filter

  Get filter

• Action
  Get group

  Get group

• Action
  Get Issue

  Returns the details of a single issue by its key or ID.

• Action
  Get Issue Comments

  Returns all comments for the specified issue.

• Action
  Get issue link

  get an issue link

• Action
  Get issue link type

  get an issue link type

• Action
  Get issue link types

  list issue link types

• Action
  Get Issue Transitions

  Returns the workflow transitions available for the specified issue.

• Action
  Get issue type

  get an issue type

• Action
  Get issue watchers

  get watchers of an issue

• Action
  Get issue worklogs

  get worklogs on an issue

• Action
  Get is watching issue bulk

  check watching status for multiple issues

• Action
  Get my filters

  Get my filters

• Action
  Get Project

  Returns the details of a single project by its key or ID.

• Action
  Get project components

  get all components of a project

• Action
  Get project versions

  get all versions of a project

• Action
  Get recent projects

  get recently viewed projects

• Action
  Get related work

  Get related work

• Action
  Get status

  Get status

• Action
  Get status category

  Get status category

• Action
  Get transitions

  get available transitions for an issue

• Action
  Get user

  get a user

• Action
  Get user groups

  get groups a user belongs to

• Action
  Get users from group

  list members of a group

• Action
  Get version

  Get version

• Action
  Get votes

  get votes on an issue

• Action
  Get worklog

  get a worklog

• Action
  Get worklogs by IDs

  get worklogs by IDs

• Action
  Get worklogs by issue ID and worklog ID

  get worklogs by issue ID and worklog ID (internal)

• Action
  List Project Issue Types

  Returns the issue types available, optionally for a given project.

• Action
  List Projects

  Returns a paginated list of projects visible to the user.

• Action
  List users

  Lists the users visible to the connected Jira account. Takes no search criterion.

• Action
  Merge versions

  merge one version into another

• Action
  Move version

  Move version

• Action
  Remove filter as favorite

  Remove filter as favorite

• Action
  Remove gadget from dashboard

  Remove gadget from dashboard

• Action
  Remove group

  Remove group

• Action
  Remove user from group

  remove a user from a group

• Action
  Restore custom field from trash

  Restore custom field from trash

• Action
  Restore deleted or archived project

  restore a deleted or archived project

• Action
  Search for dashboards

  Search for dashboards

• Action
  Search for filters

  Search for filters

• Action
  Search for issues using JQL enhanced search (GET)

  Search for issues using JQL enhanced search (GET)

• Action
  Search for issues using JQL enhanced search (POST)

  search for issues using enhanced JQL (POST)

• Action
  Search Issues (JQL)

  Searches for issues using a JQL query.

• Action
  Transition Issue

  Moves an issue to a new status by performing a workflow transition.

• Action
  Unarchive issues by keys or ID

  unarchive issues by key/ID

• Action
  Update comment

  update a comment

• Action
  Update component

  Update component

• Action
  Update custom field

  Update custom field

• Action
  Update dashboard

  Update dashboard

• Action
  Update filter

  Update filter

• Action
  Update gadget on dashboard

  Update gadget on dashboard

• Action
  Update Issue

  edit an issue

• Action
  Update issue link type

  update an issue link type

• Action
  Update issue type

  update an issue type

• Action
  Update project

  update a project

• Action
  Update project category

  update a project category

• Action
  Update related work

  Update one related-work link on a Jira project version. Reads the version's existing related work, overlays only the fields you supply, then writes the merged object back — so anything you leave blank keeps its current value.

• Action
  Update version

  Update version

• Action
  Update worklog

  update a worklog

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