Integration
Connect Sirv to NetHunt CRM
When something happens in Sirv, 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 Sirv 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 Sirv and NetHunt CRM
Triggers and actions 10 triggers · 39 actions
Trigger
New FileTriggers when a new file appears in a folder of your Sirv account, and hands on that file's name, type, size and dimensions.
Trigger
New Tagged FileTriggered when a new file carrying the chosen tag appears in your Sirv account.
Action
Add Advanced WatermarkBuilds the Sirv image URL that shows one of your images with a watermark laid over it, using the position, size, opacity and rotation you choose.
Action
Add Canvas or BorderPuts a coloured canvas and/or border around a Sirv image and returns the new image URL. Nothing is re-uploaded — the original file is untouched.
Action
Add Tags to FileAdds meta tags to a file in your Sirv account.
Action
Apply Color EffectsAdjusts the colours of a Sirv image — hue, saturation, lightness, tint, tone and levels — and returns the new image URL. The original file is untouched.
Action
Convert Spin to VideoTurns a 360 spin stored in your Sirv account into an MP4 video and returns the path of the video that was created.
Action
Convert Video to SpinConverts a video in your Sirv account into a 360-degree spin and returns the spin that was created.
Action
Copy FileCopies a file in your Sirv account to another path, leaving the original in place.
Action
Create FolderCreates an empty folder in your Sirv account at the path you give.
Action
Create ThumbnailBuilds the Sirv image URL that serves a resized, optionally cropped thumbnail of one of your images.
Action
Delete FileDeletes a file, or an empty folder, from your Sirv account.
Action
Delete file tagsRemoves one or more tags from a file in your Sirv account.
Action
Download FileDownloads a file from your Sirv account and returns its contents.
Action
Fetch File From URLPulls a file from a web address straight into your Sirv account, saving it at the path you choose, and reports whether the fetch succeeded.
Action
Find FileSearches the files in your Sirv account by name, folder, type, size, tags, description or date, and returns the matching files.
Action
Get API LimitsReturns your Sirv API rate limits and how much of each you have used.
Action
Get batch delete jobReturns the progress and results of a batch delete job you started earlier.
Action
Get CDN URLReturns the public web address of a file in your Sirv account.
Action
Get File InfoReturns the details Sirv holds on one file — its type, size, dates and image information.
Action
Get File MetadataReturns everything Sirv stores about a file: its title, description, tags, product details and any other metadata held against it.
Action
Get File TagsReturns the tags attached to a file in your Sirv account.
Action
Get product metadataReturns the product information stored on a file in your Sirv account.
Action
Get Storage InfoReturns how much storage your Sirv account is using and how much it is allowed.
Action
Get Usage ReportReturns how much your Sirv account has served — the number of file requests and the bytes transferred, broken down by day.
Action
Get ZIP JobReturns the progress and results of a zip job, including the archive it produced.
Action
List Folder ContentsLists the files and sub-folders inside a folder of your Sirv account, with each item's name, size, type and when it was last changed.
Action
Make API CallMakes any Sirv API call you specify, for endpoints that do not yet have their own action. You supply the method, the path and any data; the connected account's credentials are applied for you.
Action
Rename or Move FileRenames a file or folder, or moves it to another folder, by giving its new path.
Action
Set File MetadataSets the title, description, tags and product details held against a file in your Sirv account. Anything left blank is left as it is.
Action
Set Product MetadataAttaches product details — code, name, brand and categories — to a file in your Sirv account.
Action
Upload FileUploads a file to your Sirv account from a web address.
Action
Zip FilesStarts a job that packs the files and folders you name into a single zip in your Sirv account, and returns the job so you can check when it is ready.
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.
Each app on its own
Reviews