Integration
Connect NetHunt CRM to Gmail
When something happens in NetHunt CRM, your agent does the next thing in Gmail. 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 Gmail 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 Gmail
Triggers and actions 10 triggers · 31 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
Email SentFires when an email is sent from the mailbox (optionally filtered by query). Managed by Composio (server-side poll; ~15 min floor).
Trigger
New Gmail MessageFires when a new email arrives (optionally filtered by query/labels). Managed by Composio (server-side poll; ~15 min floor).
Action
Add Label To EmailAdds and/or removes specified gmail labels for a message; ensure `message id` and all `label ids` are valid (use 'listlabels' for custom label ids).
Action
Create Email DraftCreates a gmail email draft, supporting to/cc/bcc, subject, plain/html body (ensure `is html=true` for html), attachments, and threading.
Action
Create LabelCreates a new label with a unique name in the specified user's gmail account.
Action
Delete DraftPermanently deletes a specific gmail draft using its id; ensure the draft exists and the user has necessary permissions for the given `user id`.
Action
Delete MessagePermanently deletes a specific email message by its id from a gmail mailbox; for `user id`, use 'me' for the authenticated user or an email address to which the authenticated user has delegated access.
Action
Fetch EmailsFetches a list of email messages from a gmail account, supporting filtering, pagination, and optional full content retrieval.
Action
Fetch Message By Message IdFetches a specific email message by its id, provided the `message id` exists and is accessible to the authenticated `user id`.
Action
Fetch Message By Thread IdRetrieves messages from a gmail thread using its `thread id`, where the thread must be accessible by the specified `user id`.
Action
Get AttachmentRetrieves a specific attachment by id from a message in a user's gmail mailbox, requiring valid message and attachment ids.
Action
Get ContactsFetches contacts (connections) for the authenticated google account, allowing selection of specific data fields and pagination.
Action
Get PeopleRetrieves either a specific person's details (using `resource name`) or lists 'other contacts' (if `other contacts` is true), with `person fields` specifying the data to return.
Action
Get ProfileRetrieves key gmail profile information (email address, message/thread totals, history id) for a user.
Action
List DraftsRetrieves a paginated list of email drafts from a user's gmail account. use verbose=true to get full draft details including subject, body, sender, and timestamp.
Action
List LabelsRetrieves a list of all system and user-created labels for the specified gmail account.
Action
List ThreadsRetrieves a list of email threads from a gmail account, identified by `user id` (email address or 'me'), supporting filtering and pagination.
Action
Modify Thread LabelsAdds or removes specified existing label ids from a gmail thread, affecting all its messages; ensure the thread id is valid.
Action
Move To TrashMoves an existing, non-deleted email message to the trash for the specified user.
Action
Patch LabelPatches the specified label.
Action
Remove LabelPermanently deletes a specific, existing user-created gmail label by its id for a user; cannot delete system labels.
Action
Reply To ThreadSends a reply within a specific gmail thread using the original thread's subject, requiring a valid `thread id` and correctly formatted email addresses. supports attachments via the `attachment` parameter with valid `s3key`, `mimetype`, and `name`.
Action
Search PeopleSearches contacts by matching the query against names, nicknames, emails, phone numbers, and organizations, optionally including 'other contacts'.
Action
Send DraftSends the specified, existing draft to the recipients in the to, cc, and bcc headers.
Action
Send EmailSends an email via gmail api using the authenticated user's google profile display name, requiring `is html=true` if the body contains html and valid `s3key`, `mimetype`, `name` for any attachment.
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