Integration
Connect HigherGov to NetHunt CRM
When something happens in HigherGov, your agent does the next thing in NetHunt CRM. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want HigherGov and NetHunt CRM 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 CodeEverything your agent can do with HigherGov and NetHunt CRM
Triggers and actions 9 triggers · 18 actions
Trigger
Pursuit AddedTriggered when a new pursuit is added to your HigherGov pipeline.
Action
Find AgenciesReturns U.S. government agencies from HigherGov, with each agency's ID, name, abbreviation, type and place in the agency hierarchy. Supply an agency ID to look up a single one.
Action
Find AwardeesReturns companies that hold U.S. government awards, with each company's name, Unique Entity ID, CAGE code, address, contacts, industry codes and SAM registration dates. Filter by Unique Entity ID, CAGE code, parent company or industry code.
Action
Find Contract VehiclesReturns U.S. government contract vehicles, each with its name, description, type, status, award date and the awarding and funding agencies.
Action
Find Federal ContractsReturns U.S. federal contract awards, each with its Award ID, winning company, awarding and funding agencies, dollar values, performance dates, industry codes and place of performance. Filter by company, agency, industry code, contract vehicle or a saved HigherGov search.
Action
Find Federal GrantsReturns U.S. federal grant awards, each with its Award ID, recipient organization, awarding and funding agencies, grant program number, dollar amounts and dates. Filter by recipient, agency, program number or a saved HigherGov search.
Action
Find OpportunitiesReturns open U.S. government contract and grant opportunities, each with its title, description, posting agency, source, posted and due dates. Filter by agency, source, posted date or a saved HigherGov search.
Action
Find PeopleReturns federal, state and local government contacts, each with their name, title, email, phone and agency. Supply an email address to look up one specific person.
Action
Find PursuitsReturns the pursuits your team is tracking in HigherGov, each with its keys, name, stage and related opportunity details. Filter to a single pursuit by its key or your own reference ID.
Action
Find State and Local ContractsReturns U.S. state and local government contract awards, each with its buyer, supplier, award amount and start and end dates. Filter by date range or a saved HigherGov search.
Action
Get Opportunity DocumentsReturns the documents attached to a government opportunity, each with its file name, type, size, posted date, download link and extracted text.
Trigger
New Call LogTriggered when a new call log is added to a record in the specified folder.
Trigger
New CommentTriggered when a new comment is added to a record in the specified folder.
Trigger
New folderTriggered when a new folder is added.
Trigger
New Google Drive File in FolderPolls 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 FolderTriggered when a record is created or updated in the specified folder.
Trigger
New Record in FolderTriggered when a record is created in the specified folder.
Trigger
Two-way sync new or updated records in folderA 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 FolderTriggered when a record is updated in the specified folder.
Action
Add Call LogAdd a call log to the specified record.
Action
Add CommentAdd a comment to the specified record.
Action
Delete RecordDelete a record by ID.
Action
Find RecordSearch records in a folder by ID or text query.
Action
Find record by field valueFinds 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 FieldsList the fields of a folder.
Action
List Readable FoldersList all folders the user can read.
Action
List Writable FoldersList 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.