Integration

Connect Breeze to NetHunt CRM

When something happens in Breeze, 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.

Breeze6 triggersBreeze30 actionsNetHunt CRM8 triggersNetHunt CRM8 actions

Browse all apps

Build it

What do you want Breeze 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 Code

Everything your agent can do with Breeze and NetHunt CRM

Triggers and actions 14 triggers · 38 actions

Trigger
New Project
Triggers when a new project is created in Breeze.
Trigger
New Task
Triggers when a new task is created in the selected Breeze project.
Trigger
Project Renamed
Triggers when a Breeze project is given a new name.
Trigger
Tag Added to Task
Triggers when a tag is added to a task in the selected Breeze project.
Trigger
Task Moved
Triggers when a task is moved to a different list in the selected Breeze project.
Trigger
Task Status Updated
Triggers when a task's status changes in the selected Breeze project.
Action
Add comment
Adds a comment to a task in a Breeze project. Returns the comment that was created.
Action
Add list
Adds a new list to a Breeze project. Returns the list that was created.
Action
Add time entry
Logs a time entry against a task in a Breeze project. Returns the time entry that was created.
Action
Add todo
Adds a checklist item to a task in a Breeze project. Returns the checklist item that was created.
Action
Create New Project
Creates a new project in Breeze. Returns the project that was created.
Action
Create New Task
Creates a new task (card) in a Breeze project. Returns the task that was created.
Action
Delete card
Deletes a task (card) from a Breeze project.
Action
Delete comment
Deletes a comment from a task in a Breeze project.
Action
Delete list
Deletes a list from a Breeze project.
Action
Delete project
Deletes a project from Breeze.
Action
Delete time entry
Deletes a time entry from a task in a Breeze project.
Action
Delete todo
Deletes a checklist item from a task in a Breeze project.
Action
Find Project
Returns the Breeze projects whose name contains the text you supply.
Action
Generate time tracking report
Generates a time tracking report for a date range, optionally limited to certain projects, people, lists or tags.
Action
Get card
Returns a single task (card) from a Breeze project, including its checklists, comments count, time entries and custom field values.
Action
Get project
Returns a single Breeze project, including its budget, members and tracked time.
Action
List cards
Returns the tasks (cards) in a Breeze project, 100 per page.
Action
List comments
Returns the comments on a task in a Breeze project.
Action
List lists
Returns the lists in a Breeze project.
Action
List projects
Returns all active projects in the Breeze account.
Action
List time entries
Returns the time entries logged against a task in a Breeze project.
Action
List todos
Returns the items on a checklist of a task in a Breeze project.
Action
List users
Returns the people on your Breeze team.
Action
Move card
Moves a task to another list, or to another position within its list.
Action
Update card
Updates a task in a Breeze project. Only the values you supply are changed. Returns the updated task.
Action
Update comment
Changes the text of a comment on a task in a Breeze project. Returns the updated comment.
Action
Update list
Renames a list in a Breeze project. Returns the updated list.
Action
Update project
Updates a Breeze project. Only the values you supply are changed. Returns the updated project.
Action
Update time entry
Updates a time entry on a task in a Breeze project. Only the values you supply are changed. Returns the updated time entry.
Action
Update todo
Updates a checklist item on a task in a Breeze project. Only the values you supply are changed. 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.

Each app on its own

The other way round: NetHunt CRM to Breeze