Integration
Connect Gravity Forms to NetHunt CRM
When something happens in Gravity Forms, 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 Gravity Forms 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 Gravity Forms and NetHunt CRM
Triggers and actions 9 triggers · 38 actions
Trigger
Form SubmissionTriggers when the specified form is submitted.
Action
Add Entry NoteAdds a note to a form entry. Use it to write a progress record back onto a submission — for example noting that the submission was synced to your CRM, who handled it, or why it was skipped — so the note is visible to anyone reviewing that entry in WordPress.
Action
Create EntryCreates a new form entry.
Action
Create FeedAttaches a new add-on feed to a form. A feed is one add-on's configuration on a form — the rule that says what should happen when the form is submitted, such as creating a WordPress user, adding the person to a mailing list, or taking a payment.
Action
Create FormCreates a new form on the WordPress site and returns its id. Supply the form's title and, if you want the form ready to collect data, the fields it should show.
Action
Create Form FeedAttaches a new add-on feed to a named form. Does the same thing as Create Feed, but takes the form as part of the address rather than in the settings — use whichever reads better in your automation.
Action
Delete EntryRemoves a form entry. By default the entry is moved to the trash and can still be restored from the Entries list; you can choose instead to delete it outright so it cannot be recovered.
Action
Delete FeedPermanently removes an add-on feed from a form, so that add-on no longer acts on the form's submissions. The form itself and its entries are untouched.
Action
Delete FormMoves a form to the trash on the WordPress site. The form stops accepting submissions and disappears from the forms list, and the site owner can still restore it or empty the trash in WordPress.
Action
Delete NotePermanently removes an entry note. Use it to clear a note you logged against a submission, for example after a failed sync was retried successfully.
Action
Get EntryRetrieve a single form entry, including every field value the person submitted.
Action
Get FeedReturns one add-on feed by its id, including the add-on's settings. A feed is one add-on's configuration attached to a form — the rule that says what should happen when the form is submitted.
Action
Get FormReturns one form's full definition, including every field on it, its notifications and its confirmations. Use it to read a form's field ids and labels before mapping data into that form.
Action
Get Form ResultsReturns the summarised answers for a survey, quiz or poll form — how many people picked each choice, and how many answered each free-text question — rather than the individual entries. On a form with a lot of entries the summary is built in the background, so the result can come back marked as still being calculated.
Action
Get NoteReturns a single entry note by its id, including the note text, the entry it belongs to, when it was recorded and who it is credited to.
Action
List EntriesReturns form entries from across every form on the site, newest first, and can narrow the results to one form or to entries whose answer to a chosen question matches a value you give.
Action
List Entry NotesReturns every note attached to one form entry — both notes people have added and the notes Gravity Forms records automatically, such as notification failures. Use it to read back what has already been logged against a submission.
Action
List FeedsReturns every add-on feed configured on the site. A feed is one add-on's configuration attached to a form — the rule that says what should happen to a submission, such as sending it to a mailing list or charging a payment.
Action
List Form EntriesReturns the entries submitted on one particular form, newest first, and can narrow them to entries whose answer to a chosen question matches a value you give.
Action
List Form FeedsReturns the add-on feeds attached to one form — the rules that say what happens when that form is submitted. Returns an empty list when the form has no feeds.
Action
List FormsReturns every active form on the WordPress site, with each form's id, title and entry count. Use it to look up the id a form needs before working with that form's entries.
Action
List NotesReturns every entry note on the site, across all forms and entries. Use it to sweep recently logged notes when you do not already know which entry you are looking for; to read the notes on one known entry, use List Entry Notes instead.
Action
Send Entry NotificationsSends the notification emails an entry's form is set up to send, for an entry that already exists — useful for re-sending a confirmation, or for notifying people about an entry that was created through the API rather than by someone filling the form in.
Action
Submit FormSubmit a form the way a visitor would — Gravity Forms runs the form's own validation, saves the entry, and fires its notifications and confirmation.
Action
Update EntryChange the answers on an existing form entry. Answers you leave blank keep the values they already have.
Action
Update Entry PropertiesChanges an entry's housekeeping flags without touching any of its answers — whether it is starred, whether it counts as read, and whether it sits in the active list, the trash or spam.
Action
Update FeedChanges an existing add-on feed's settings. Settings you do not include are left as they are, so you can change one thing without restating the rest of the add-on's configuration.
Action
Update Feed PropertiesSwitches an add-on feed on or off, and sets the order it runs in. The add-on's own settings are left completely untouched, so this is the safe way to pause a feed without risking its configuration.
Action
Update FormReplaces an existing form's definition with the one you supply. Gravity Forms overwrites the whole form, so read the form first with Get Form and send back every part of it you want to keep.
Action
Update NoteReplaces the text of an existing entry note. Use it to revise a note you logged earlier against a submission — for example updating "Sync started" to "Synced to CRM as contact 4821".
Action
Validate SubmissionChecks a set of answers against a form's own validation rules without saving an entry or sending any notifications. Returns whether the answers would be accepted, and the per-field error messages when they would not.
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.