Connect Asana to NetHunt CRM

Both apps 50Asana 34NetHunt CRM 16

• Trigger
  Completed task in project

  Triggered when any task is completed in the selected project.

• Trigger
  New comment on task

  Triggered when any new comment is made to the selected task.

• Trigger
  New or updated task in project

  Triggered when any task is added or updated in the specified project in the specified workspace.

• Trigger
  New project in workspace

  Triggered when a new project is added to the selected workspace.

• Trigger
  New story on task

  Triggered when any new story is made to the selected task.

• Trigger
  New tag in workspace

  Triggered when a new tag is added to the selected workspace.

• Trigger
  New task assigned to you in workspace

  Triggered when a task is assigned to you in the selected workspace.

• Trigger
  New team in workspace

  Triggered when a new team is added to the selected workspace.

• Trigger
  New user

  Triggered when a new user is created.

• Trigger
  New workspace

  Triggered when a new workspace is created.

• Action
  Add attachment

  Upload an attachment to a task. POST /attachments (multipart, parent=task_gid).

• Action
  Add tag to task

  Adds an existing tag to a task.

• Action
  Add task to section

  Moves a task into a section of a project.

• Action
  Associate task to project

  Associates a newly created task to a specified project in the specified workspace.

• Action
  Complete task

  Marks a task as completed.

• Action
  Create new comment

  Creates a new comment on the specified task.

• Action
  Create new project

  Creates a new project in the specified workspace.

• Action
  Create new task

  Creates a new task in a workspace or project.

• Action
  Create section in project

  Creates a new section within a project.

• Action
  Create subtask

  Creates a subtask under an existing parent task.

• Action
  Delete comment

  Delete a comment (story) by gid. DELETE /stories/{story_gid}.

• Action
  Delete project

  Delete a project by gid. DELETE /projects/{project_gid}.

• Action
  Delete task

  Permanently deletes a task.

• Action
  Duplicate task

  Creates a copy of an existing task.

• Action
  Find tasks in project

  Returns the tasks belonging to a project.

• Action
  Get project

  Fetch a single project by its gid. GET /projects/{project_gid}.

• Action
  Get task by ID

  Returns a single task's details by its ID.

• Action
  Get user

  Fetch a single user by gid (or 'me'). GET /users/{user_gid}.

• Action
  List attachments

  List attachments on a task. GET /attachments?parent={task_gid}.

• Action
  List projects

  List projects in a workspace, optionally filtered by team. GET /workspaces/{workspace_gid}/projects.

• Action
  List users

  List users in a workspace. GET /workspaces/{workspace_gid}/users (or GET /users).

• Action
  Remove tag from task

  Removes a tag from a task.

• Action
  Update project

  Update a project's fields (name, notes, due date, etc). PUT /projects/{project_gid}.

• Action
  Update task

  Updates an existing task's fields.

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

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