Integration
Connect NetHunt CRM to Bitly
When something happens in NetHunt CRM, your agent does the next thing in Bitly. 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 Bitly 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 Bitly
Triggers and actions 16 triggers · 33 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.
Trigger
New Bitlink in GroupTriggers when a new Bitlink appears in the group.
Trigger
New Branded Short DomainTriggers when a new branded short domain is added.
Trigger
New ChannelTriggers when a new channel is created.
Trigger
New GroupTriggers when a new group is created.
Trigger
New OrganizationTriggers when a new organization is created.
Trigger
New QR Code in GroupTriggers when a new QR code appears in the group.
Trigger
New Sorted Bitlink in GroupTriggers when a new Bitlink appears in the group's sorted ranking.
Trigger
New Tag in GroupTriggers when a new tag appears in the group.
Action
Add Custom Bitlinkcreate a custom (branded) Bitlink
Action
Bulk update bitlinksbulk update Bitlinks in a group
Action
Create an inline CSV export for a groupcreate an inline CSV export for a group
Action
Create BitlinkShortens a long URL into a Bitlink. Optionally set a title and a branded custom domain.
Action
Delete a Bitlinkdelete a Bitlink
Action
Expand BitlinkReturns the long destination URL for a Bitlink ID (e.g. bit.ly/abc123).
Action
Generate a static QR Code imagegenerate a static QR code image
Action
Get Group Limit UsageReturns a Bitly group's current feature limit usage, with the count used for each limit.
Action
Get Plan LimitsReturns all plan limits and their current usage counts for a Bitly organization.
Action
Get Platform LimitsReturns the organization's platform limits and current usage counts per API endpoint.
Action
Get QR Code ImageFetches a QR code's rendered image by QR code ID. The image is saved to APIANT temporary storage and returned as a file reference, so it can be emailed, uploaded or attached in a later step. An error occurs if the QR code is not found.
Action
Get Top Links and QR Codes by EngagementReturns a group's top-performing bitlinks and decoupled QR codes ranked by engagement count over a chosen reporting window.
Action
Retrieve BitlinkFetches the details of a single Bitlink by its ID (e.g. bit.ly/abc123).
Action
Retrieve Custom BitlinkReturns the Bitlink that a custom (branded) short link points to, along with that Bitlink's details — destination URL, title, tags, and created timestamp. An error occurs if the custom Bitlink is not found.
Action
Retrieve GroupFetches a single Bitly group (workspace) by its GUID, returning the group's name, organization, role, status, and branded short domains. An error occurs if the group is not found.
Action
Retrieve Group PreferencesFetches the preferences for a single Bitly group (workspace) by its GUID, returning the group's default short domain. An error occurs if the group is not found.
Action
Retrieve OrganizationFetches a single Bitly organization by its GUID, returning the organization's name, subscription tier, role, status, and branded short domains. An error occurs if the organization is not found.
Action
Retrieve QR CodeReturns the details of a single QR code by its ID — title, the Bitlink and destination URLs it encodes, its type, tags, and created/updated timestamps. This returns the QR code's information only, not the scannable image file; use Get QR Code Image for that. An error occurs if the QR code is not found.
Action
Retrieve UserReturns the Bitly user account the connection is authenticated as, including its login, name, email addresses, activity flags and default group.
Action
Shorten a Linkshorten a long URL into a Bitlink
Action
Update a Groupupdate a group
Action
Update a QR Codeupdate a QR code
Action
Update a Userupdate the authenticated user
Action
Update BitlinkUpdates a Bitlink's title, tags, or archived state.
Action
Update Group Preferencesupdate group preferences
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