NetHunt CRM
Connect your client's NetHunt CRM with a key they paste, and call its API through Operate As.
- Website
- nethunt.com
- Connects by
- Pasting a Email and API key
- Category
- CRM and sales
- Services
- 1
- Tools
- Pass-through only
| Service | Key | Base URL |
|---|---|---|
| NetHunt CRM | nethunt-crm | https://nethunt.com/api/v1/zapier |
Connecting
Your client makes a Email and API key in their NetHunt CRM settings and pastes it on their link. Operate As tries it with NetHunt CRM before saving it, and stores it encrypted. See Services connected with an API key.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "nethunt-crm" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| Use the NetHunt CRM key you paste, with only the access you gave that key | Chosen on the provider's screen |
Pass-through
NetHunt CRM has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.
Add the client
In Clients, add your client and select NetHunt CRM. Then send them their link.
Your client connects
They paste a Email and API key from their NetHunt CRM settings.
Find the endpoint
Pick the call from NetHunt CRM's own API docs. Your path is everything after https://nethunt.com/api/v1/zapier.
Send it through Operate As
Use the client's ID, the service key nethunt-crm and that path. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../nethunt-crm/triggers/readable-folder" \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
A key works until your client deletes it in NetHunt CRM. They can paste a new one on the same link at any time, and your workflows carry on without changes.
See Keeping access alive and Removing access.
{ "status": 401, "data": { "…": "the service's own error" }, "encoding": "json"}