Integration
Connect Freedcamp to NetHunt CRM
When something happens in Freedcamp, 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 Freedcamp 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 Freedcamp and NetHunt CRM
Triggers and actions 13 triggers · 23 actions
Trigger
New IssueTriggers when a new issue is filed in Freedcamp's issue tracker. The project must have the Issue Tracker app enabled.
Trigger
New MilestoneTriggers when a new milestone is created in Freedcamp. The project must have the Milestones app enabled.
Trigger
New Project CreatedTriggers when a new project is created in your Freedcamp account.
Trigger
Task Assigned to MeTriggers when a task assigned to you appears in Freedcamp.
Trigger
Task CompletedTriggers when a Freedcamp task is marked completed.
Action
Add CommentAdds a comment to a Freedcamp task and returns the created comment, including its direct link.
Action
Add Discussion CommentAdds a comment to a Freedcamp discussion and returns the created comment, including its direct link.
Action
Create ProjectCreates a new Freedcamp project and returns it. Put it in an existing project group by ID, or name a group and Freedcamp creates it.
Action
Create TaskCreates a task in a Freedcamp project and returns it, including its direct link. Optionally set the list, priority, assignee, dates, a parent task or a recurrence rule.
Action
Get Current UserReturns the Freedcamp account the connection belongs to: the signed-in user's ID and profile, plus the projects and project groups they can see.
Action
Get ProjectReturns one Freedcamp project by ID, including its group, your role, the apps enabled on it, its members and any custom fields.
Action
Get TaskReturns one Freedcamp task by ID, including its list, priority, status, assignee, dates and comments.
Action
Get TasksReturns Freedcamp tasks, optionally filtered by project, status, assignee or due-date range. Custom field values are included.
Action
List IssuesReturns issues from a Freedcamp project's issue tracker, optionally filtered by type, priority, status, assignee or due-date range. The project must have the Issue Tracker app enabled.
Action
List MilestonesReturns milestones from Freedcamp, optionally filtered by project, status, assignee or due-date range. The project must have the Milestones app enabled.
Action
List Time RecordsReturns logged time records from Freedcamp, optionally filtered by project, user or date range. The project must have the Time Tracking app enabled.
Action
List UsersReturns the Freedcamp users you share projects with, or just the members of one project when you supply a project ID.
Action
NotificationsReturns the unread notifications for a Freedcamp project, optionally limited to items you follow.
Action
Show ProjectsReturns every Freedcamp project you can see, with its group, color, permissions and enabled apps.
Action
Update TaskUpdates an existing Freedcamp task. Only the fields you fill in are changed.
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.