Integration
Connect OpenAI to NetHunt CRM
When something happens in OpenAI, 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 OpenAI 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 OpenAI and NetHunt CRM
Triggers and actions 13 triggers · 77 actions
Trigger
New batchList your organization's batches.
Trigger
New fileReturns a list of files.
Trigger
New modelLists the currently available models.
Trigger
New vector storeReturns a list of vector stores.
Trigger
New videoList recently generated videos for the current project.
Action
Cancel batchCancels an in-progress batch.
Action
Cancel runCancels a run that is in_progress.
Action
Cancel vector store file batchCancel a vector store file batch.
Action
Content moderationClassifies text for hate, harassment, self-harm, sexual, and violence categories using the Moderations API.
Action
Count input tokensReturns input token counts of the request.
Action
Create assistantCreate an assistant with a model and instructions.
Action
Create chat completionSends a list of chat messages to a model via the Chat Completions API and returns the assistant's reply.
Action
Create completionCreates a completion for the provided prompt and parameters.
Action
Create embeddingGenerates a vector embedding for input text using an embeddings model (e.g. text-embedding-3-small).
Action
Create messageCreate a message.
Action
Create runCreate a run.
Action
Creates and executes a batch from an uploaded file of requestsCreates and executes a batch from an uploaded file of requests
Action
Create threadCreate a thread.
Action
Create thread and runCreate a thread and run it in one request.
Action
Create vector storeCreate a vector store.
Action
Create vector store fileCreate a vector store file by attaching a File to a vector store.
Action
Create vector store file batchCreate a vector store file batch.
Action
Create video edit jobCreate a new video generation job by editing a source or existing generated video.
Action
Create video extensionCreate an extension of a completed video.
Action
Create video generation jobCreate a new video generation job from a prompt and optional reference assets.
Action
Create video remixCreate a remix of a completed video using a refreshed prompt.
Action
Delete assistantDelete an assistant.
Action
Delete eval runDelete an eval run.
Action
Delete fileDelete a file and remove it from all vector stores.
Action
Delete messageDeletes a message.
Action
Delete threadDelete a thread.
Action
Delete vector storeDelete a vector store.
Action
Delete vector store fileDelete a vector store file (removes from store, file itself not deleted).
Action
Delete videoPermanently delete a completed or failed video and its stored assets.
Action
Download video contentDownload the generated video bytes or a derived preview asset.
Action
Edit imageCreates an edited or extended image given one or more source images and a prompt.
Action
Generate imageGenerates an image from a text prompt using gpt-image-1 / DALL-E and returns the image URL or base64 data.
Action
Generate speechConverts text into spoken audio using a TTS model and the selected voice. Returns audio bytes.
Action
Get assistantRetrieves an assistant.
Action
Get batchRetrieves a batch.
Action
Get fileReturns information about a specific file.
Action
Get file contentReturns the contents of the specified file.
Action
Get messageRetrieve a message.
Action
Get modelRetrieves a model instance.
Action
Get runRetrieves a run.
Action
Get run stepRetrieves a run step.
Action
Get threadRetrieves a thread.
Action
Get vector storeRetrieves a vector store.
Action
Get vector store fileRetrieves a vector store file.
Action
Get vector store file batchRetrieves a vector store file batch.
Action
Get vector store file contentRetrieve the parsed contents of a vector store file.
Action
Get videoFetch the latest metadata for a generated video.
Action
List conversation itemsList all items for a conversation with the given ID.
Action
List filesLists files that have been uploaded to your OpenAI account.
Action
List messagesReturns a list of messages for a given thread.
Action
List modelsLists the models currently available to your account.
Action
List runsReturns a list of runs belonging to a thread.
Action
List run stepsReturns a list of run steps belonging to a run.
Action
List vector store file batch filesReturns a list of vector store files in a batch.
Action
List vector store filesReturns a list of vector store files.
Action
OpenAI agent messageRuns one AI agent turn on OpenAI and returns the model's reply. The turn is billed to the OpenAI account connected on this step, and the agent can call the account's AI tool automations.
Action
Retrieve responseRetrieves a previously created model response by its Response ID.
Action
Search vector storeSearch a vector store for relevant chunks based on a query and filter.
Action
Send model a messageSends a message to an OpenAI model via the Responses API and emits its response. Returns a Response ID usable as previous_response_id for multi-turn conversations.
Action
Submit tool outputs to runSubmit tool outputs when a run requires action.
Action
Transcribe audioTranscribes audio into the input language.
Action
Translate audioTranslates audio into English.
Action
Update assistantModifies an assistant.
Action
Update messageModifies a message.
Action
Update runModifies a run.
Action
Update threadModifies a thread.
Action
Update vector storeModifies a vector store.
Action
Update vector store file attributesUpdate attributes on a vector store file.
Action
Upload fileUpload a file that can be used across various endpoints.
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