Connect Expiration Reminder to NetHunt CRM

Both apps 34Expiration Reminder 18NetHunt CRM 16

• Trigger
  New Contact

  Triggered when a new contact is added to your Expiration Reminder account.

• Trigger
  New Expiration Item

  Triggered when a new expiration item is added to your Expiration Reminder account.

• Trigger
  Status Changed Expiration Item

  Triggered when an expiration item's status changes in Expiration Reminder — for example when it moves from active to expiring or expired.

• Action
  Add Location

  Creates a location in Expiration Reminder, optionally nested under a parent location and assigned to a team. Any custom fields defined on locations in your account can be set too. Returns the created location.

• Action
  Create Contact

  Creates a contact in Expiration Reminder with their email, contact details, type, location and team, plus any custom fields defined on contacts in your account. Returns the created contact.

• Action
  Create Expiration Item

  Creates an expiration item in Expiration Reminder with its name and expiration date, optionally attaching contacts, locations, tags, a category and an assignee, plus any custom fields defined in your account. Returns the created item.

• Action
  Create Expiration Item for Contact

  Creates an expiration item in Expiration Reminder and attaches it to a specific contact, with its name, expiration date and category, plus any custom fields defined in your account. Returns the created item.

• Action
  Delete Contact

  Deletes a contact from Expiration Reminder. Returns the contact record that was deleted.

• Action
  Delete Expiration Item

  Deletes an expiration item from Expiration Reminder. Returns the item record after deletion.

• Action
  Find Contact

  Returns the Expiration Reminder contacts matching a search term or an exact email address, with the total number of matches.

• Action
  Find Expiration

  Returns the Expiration Reminder expiration items matching a search term and status, with the total number of matches.

• Action
  Get Contact

  Returns a single Expiration Reminder contact by its id, including their contact details, assignment, location and every custom field stored on them.

• Action
  Get Expiration Item

  Returns a single Expiration Reminder expiration item by its id, including its category, contacts, locations, tags, attachments and every custom field stored on it.

• Action
  List Contacts

  Returns the contacts in your Expiration Reminder account, with the total number of contacts.

• Action
  List Expiration Items

  Returns the expiration items in your Expiration Reminder account, optionally limited to one status, with the total number of items.

• Action
  List Locations

  Returns the locations in your Expiration Reminder account, with the total number of locations.

• Action
  Renew Expiration

  Renews an Expiration Reminder expiration item by moving it to a new expiration date. Returns the renewed item.

• Action
  Update Expiration Item

  Updates an existing Expiration Reminder expiration item. Fields you leave blank are left unchanged; custom fields defined in your account can be set too. Returns the updated item.

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