Integration
Connect NetHunt CRM to Carbon Intensity
When something happens in NetHunt CRM, your agent does the next thing in Carbon Intensity. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want NetHunt CRM and Carbon Intensity 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 NetHunt CRM and Carbon Intensity
Triggers and actions 8 triggers · 21 actions
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.
Action
Get carbon intensity factorsGet the carbon intensity emission factors used for each generation fuel type.
Action
Get national carbon intensityGet the current and next half-hourly carbon intensity forecast and actual values for Great Britain.
Action
Get national carbon intensity between two timesGet the national carbon intensity values for every settlement period between two given date/times.
Action
Get national carbon intensity by dateGet the half-hourly national carbon intensity values for every settlement period on a given date.
Action
Get national carbon intensity by date and periodGet the national carbon intensity value for a specific settlement period on a given date.
Action
Get national carbon intensity from a timeGet the national carbon intensity reading for the half-hour settlement period containing a given date/time.
Action
Get national carbon intensity statisticsGet the average, max, min and index carbon intensity statistics between two given date/times, optionally in fixed time blocks.
Action
Get national generation mixGet the current national electricity generation mix by fuel type as a percentage.
Action
Get national generation mix between two timesGet the national electricity generation mix by fuel type for a given date/time range.
Action
Get regional carbon intensityGet the current carbon intensity for GB regions, England, Scotland, and Wales.
Action
Get regional carbon intensity between two timesGet the regional carbon intensity forecast for every GB region between two given date/times.
Action
Get regional carbon intensity by postcodeGet the current and forecast carbon intensity for the region containing a given GB postcode.
Action
Get regional carbon intensity by region IDGet the current and forecast carbon intensity for a specific GB DNO region by its region ID.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews