Integration

Connect NetHunt CRM to NHL Records and Stats

When something happens in NetHunt CRM, your agent does the next thing in NHL Records and Stats. Describe it in plain language and the automation is built, tested on every branch and kept running.

NetHunt CRM8 triggersNetHunt CRM8 actionsNHL Records and Stats13 actions

Browse all apps

Build it

What do you want NetHunt CRM and NHL Records and Stats to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with NetHunt CRM and NHL Records and Stats

Triggers and actions 8 triggers · 21 actions

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.
Action
Find draft picks
Search historical NHL draft picks, filterable by draft year, drafting team, and round number.
Action
Find player milestones
Find players meeting a career or single-season milestone (e.g. 1000-point career, 500-goal career, 100-point season, 50-goal season, 5-goal game).
Action
Find playoff series
Search game-by-game data for a specific playoff round and season (e.g. Stanley Cup Final).
Action
Get attendance records
Return league-wide season attendance records, split into regular-season and playoff attendance.
Action
Get franchise detail
Return a franchise's captain history, coaching history, general manager history, and retired numbers.
Action
Get franchise record vs another franchise
Return a franchise's all-time regular-season record against every other team in the league.
Action
Get franchise team totals
Return cumulative all-time stats (wins, losses, ties, road/home splits, etc) for every franchise.
Action
Get playoff record vs another franchise
Return a franchise's all-time playoff record against every other team in the league.
Action
List franchises
List every franchise in NHL history with its id, name, and first/last season.
Action
List franchise season results
List every season's win/loss result for a specific franchise, sortable by season.
Action
List officials
List NHL officials, optionally filtered to only currently active officials.
Action
List players by team
List every player who has played for a specified team.
Action
List trophies
List every NHL trophy with its description and image.

Each app on its own

The other way round: NHL Records and Stats to NetHunt CRM