Integration

Connect NetHunt CRM to Open Government, Argentina

When something happens in NetHunt CRM, your agent does the next thing in Open Government, Argentina. Describe it in plain language and the automation is built, tested on every branch and kept running.

NetHunt CRM8 triggersNetHunt CRM8 actionsOpen Government, Argentina10 actions

Browse all apps

Build it

What do you want NetHunt CRM and Open Government, Argentina 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 Code

Everything your agent can do with NetHunt CRM and Open Government, Argentina

Triggers and actions 8 triggers · 18 actions

Trigger
New Call Log
Triggered when a new call log is added to a record in the specified folder.
Trigger
New Comment
Triggered when a new comment is added to a record in the specified folder.
Trigger
New folder
Triggered when a new folder is added.
Trigger
New Google Drive File in Folder
Polls 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 Folder
Triggered when a record is created or updated in the specified folder.
Trigger
New Record in Folder
Triggered when a record is created in the specified folder.
Trigger
Two-way sync new or updated records in folder
A 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 Folder
Triggered when a record is updated in the specified folder.
Action
Add Call Log
Add a call log to the specified record.
Action
Add Comment
Add a comment to the specified record.
Action
Delete Record
Delete a record by ID.
Action
Find Record
Search records in a folder by ID or text query.
Action
Find record by field value
Finds 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 Fields
List the fields of a folder.
Action
List Readable Folders
List all folders the user can read.
Action
List Writable Folders
List folders the user can create records in.
Action
Find datasets
Search Argentina's open-data catalog (datos.gob.ar) by keyword, filter, or facet and return matching datasets. Uses the CKAN package_search action.
Action
Find resources
Search for downloadable resources (files/URLs) attached to datasets in the catalog. Uses the CKAN resource_search action.
Action
Get dataset
Retrieve a dataset's full metadata and its list of resources by id or slug. Uses the CKAN package_show action.
Action
Get group
Retrieve a dataset group's metadata by id or slug. Uses the CKAN group_show action.
Action
Get organization
Retrieve a publishing organization's (government body's) metadata by id or slug. Uses the CKAN organization_show action.
Action
Get resource
Retrieve a single dataset resource's metadata (file URL, format, size) by id. Uses the CKAN resource_show action.
Action
List datasets
List the ids of all datasets published in the catalog. Uses the CKAN package_list action.
Action
List groups
List the dataset groups defined in the catalog. Uses the CKAN group_list action.
Action
List organizations
List the government organizations that publish datasets in the catalog. Uses the CKAN organization_list action.
Action
List tags
List the tags used to classify datasets in the catalog. Uses the CKAN tag_list action.

Each app on its own

The other way round: Open Government, Argentina to NetHunt CRM