Integration
Connect NetHunt CRM to Temsor
When New Call Log fires in NetHunt CRM, your agent runs Get call in Temsor. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want NetHunt CRM and Temsor to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What NetHunt CRM can start in Temsor
When New Call Log in NetHunt CRM
then Get call in Temsor
When New Comment in NetHunt CRM
then Verify email in Temsor
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with NetHunt CRM and Temsor
Triggers and actions 8 triggers · 19 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.
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.
Action
Close promiseMarks an open call promise as kept or broken, with an optional short note, and returns the updated promise.
Action
Find calls by querySearches the call archive and returns the calls, call promises and extracted facts that match a text query, optionally narrowed by promise status, extension, competitor, date range or the extension a promise got stuck at.
Action
Get callReturns one call by its id, including its transfer path, handoff graph and count of open promises.
Action
List callsReturns the most recent calls in your Temsor call archive, with each call's direction, trunk, summary, transfer path and open promise count.
Action
List personsReturns the people seen in your call history — callers with their phones and names, and extensions seen on transfers — optionally filtered by call, kind or search text.
Action
List promisesReturns the call promises tracked for agent handoff, filtered by status (open by default), each with its caller, promise text, transfer path and where it got stuck.
Action
Redact textErases a caller's personal data from the Temsor call index — a promise, call, person, fact or utterance by id, or everything linked to a caller's phone number — by anonymizing or deleting it, and records an audit entry.
Action
Validate IBANValidates an IBAN from any of 70+ countries, checking its checksum, country length and account structure, and returns the bank and branch codes plus a corrected suggestion when only the check digits are wrong.
Action
Validate phone numberValidates a phone number and returns it in standard international (E.164) and national form, with its country and line type.
Action
Validate Turkish IDValidates a Turkish identifier — national ID (TCKN), tax number (VKN), IBAN, licence plate, IMEI, barcode, KEP address, MERSİS number, postal code or ISBN — detecting the type automatically when you don't specify it, and returns whether it is valid plus resolved details.
Action
Verify emailChecks an email address: its syntax, whether the domain can receive mail, whether it is disposable or a role account, and suggests a correction for common domain typos.
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
What our customers say
More from NetHunt CRM
NetHunt CRM to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
NetHunt CRM to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
NetHunt CRM to StripeStripe is a payment processing platform for online businesses.
NetHunt CRM to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
NetHunt CRM to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
NetHunt CRM to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Temsor
HubSpot to TemsorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TemsorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TemsorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TemsorGoogle Sheets
Gmail to TemsorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TemsorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
NetHunt CRM and Temsor, answered
What can start an automation from NetHunt CRM?
Any of NetHunt CRM's 8 triggers in the catalog, including New Call Log, New Comment, New folder and New Google Drive File in Folder. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Temsor when something happens in NetHunt CRM?
Any of Temsor's 11 actions, including Close promise, Find calls by query, Get call and List calls. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Temsor to NetHunt CRM?
Temsor has no triggers in the catalog today, so automations start in NetHunt CRM. If you need the other direction, ask: your agent reads Temsor's API documentation and adds it.
Do I have to build a connector for NetHunt CRM or Temsor?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use NetHunt CRM and Temsor without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.