Connect Agile CRM to NetHunt CRM

Both apps 89Agile CRM 73NetHunt CRM 16

• Trigger
  List all tasks

  list all tasks, surfacing new ones over time

• Trigger
  List contacts

  list contacts, surfacing new ones over time

• Trigger
  List deals

  list deals/opportunities, surfacing new ones over time

• Trigger
  List events

  list events, surfacing new ones over time

• Trigger
  List pending tasks

  list pending tasks within N days

• Trigger
  List tickets

  list help desk tickets by filter, surfacing new ones

• Trigger
  List tracks

  list deal tracks/pipelines

• Trigger
  New contact

  Triggered when a new contact is added. Polls the contacts list and emits each new contact, deduplicated by contact id.

• Trigger
  New matching contact or company

  Triggers when a new contact or company matches your search query.

• Trigger
  New matching task

  Triggers when a new task matches your filter.

• Action
  Add contact to campaign

  enroll a contact into a campaign by email

• Action
  Add lead score by email

  add lead score to a contact by email

• Action
  Add note by contact email

  add a note to a contact by email

• Action
  Add tags by contact email

  add tags to a contact by email

• Action
  Add tags to contact

  add multiple tags to a contact by ID

• Action
  Add tag to contact

  Adds a tag to the specified contact. Spaces in the tag are replaced with underscores.

• Action
  Add ticket note

  add a note to a ticket

• Action
  Change contact owner

  change the owner of a contact

• Action
  Create company

  /contacts (type=company) — create a company record

• Action
  Create contact

  create a full contact record

• Action
  Create deal

  create a deal/opportunity

• Action
  Create deal by contact email

  create a deal for a contact by email

• Action
  Create deal note

  create a note on a deal

• Action
  Create document

  create a document

• Action
  Create event

  create an event

• Action
  Create new contact (just email)

  Creates a new contact using just the email address, then returns the new Contact ID.

• Action
  Create note

  create a note

• Action
  Create task

  create a task

• Action
  Create task by email

  create a task for a contact by email

• Action
  Create ticket

  create a help desk ticket

• Action
  Delete company

  Delete a company.

• Action
  Delete contact

  delete a contact

• Action
  Delete contact note

  delete a contact note

• Action
  Delete deal

  delete a deal

• Action
  Delete event

  delete an event

• Action
  Delete tags by contact email

  remove tags from a contact by email

• Action
  Delete task

  delete a task

• Action
  Delete ticket

  delete a help desk ticket

• Action
  Find contact

  Returns the Contact ID (and contact record) for the given email address.

• Action
  Get company by ID

  Retrieve a company by ID.

• Action
  Get contact by ID

  retrieve a contact by ID

• Action
  Get contact by phone

  look up a contact by phone

• Action
  Get contact deals

  list deals for a contact

• Action
  Get contact documents

  list documents for a contact

• Action
  Get contact events

  list events for a contact

• Action
  Get contact notes

  list notes for a contact

• Action
  Get contact tasks

  list tasks for a contact

• Action
  Get deal by ID

  retrieve a deal by ID

• Action
  Get deal notes

  list notes for a deal

• Action
  Get deals by pipeline

  list deals grouped by pipeline

• Action
  Get deals from track

  list deals filtered by track

• Action
  Get Deals Grouped by Milestone

  Returns every deal in the account, grouped into one list per milestone (New, Won, Lost and any custom milestones). Takes no search criteria — pick the milestone you want out of the returned groups.

• Action
  Get my deals

  list deals owned by the current user

• Action
  Get task by ID

  retrieve a task by ID

• Action
  Get ticket filters

  list available ticket filters

• Action
  Get ticket messages

  list notes/messages for a ticket

• Action
  List companies

  list companies

• Action
  Remove contact from deal

  remove a contact from a deal

• Action
  Remove tag from contact

  Removes a tag from the specified contact. Spaces in the tag are replaced with underscores.

• Action
  Remove tags from contact

  remove multiple tags from a contact by ID

• Action
  Search contact by email

  look up a contact by email

• Action
  Search contact by email (POST)

  look up a contact by email (POST variant)

• Action
  Search contacts by dynamic filter

  search contacts by dynamic filter

• Action
  Update company

  /contacts/edit-properties (company) — update company properties

• Action
  Update contact

  Updates the specified contact's first name, last name, and email properties.

• Action
  Update contact lead score

  update a contact's lead score

• Action
  Update contact property

  update contact properties

• Action
  Update contact star rating

  update a contact's star rating

• Action
  Update deal

  partially update a deal

• Action
  Update deal note

  Update a note on a deal. Fetches the deal, finds the note, overlays ONLY the fields you supply (blank fields keep their current value), then saves. Non-destructive.

• Action
  Update event

  Update an event. Fetches the existing event, overlays ONLY the fields you supply (blank fields are left untouched), and carries the attached contacts through, then saves. Non-destructive.

• Action
  Update task

  partially update a task

• Action
  Update track

  Update a track (milestone pipeline). Fetches the track, overlays ONLY the fields you supply (blank fields keep their current value, so the milestone list is never erased), then saves. Non-destructive.

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