Sign In Get Early Access
Integrations

Nexwatt speaks your stack.

Pre-built connectors for the tools your ops team already runs. Six categories: CRM, project management, communication, spreadsheets and databases, HR and finance, and custom REST APIs. If it has an API, the agent can call it.

CRM
PM
COMMS
SHEETS
HR
API

24 pre-built connectors. New ones added based on demand.

SF
Salesforce
Read / Write
Connected via API
HS
HubSpot
Read / Write
Connected via API
PD
Pipedrive
Read / Write
Connected via API
ZD
Zendesk
Read / Write
Connected via API
JR
Jira
Read / Write
Connected via API
LN
Linear
Read / Write
Connected via API
AS
Asana
Read / Write
Connected via API
CL
ClickUp
Read / Write
Connected via API
SL
Slack
Write / Trigger
Connected via API
MS
Microsoft Teams
Write / Trigger
Connected via API
GM
Gmail
Read / Write
Connected via API
OT
Outlook
Read / Write
Connected via API
GS
Google Sheets
Read / Write
Connected via API
AT
Airtable
Read / Write
Connected via API
NT
Notion
Read / Write
Connected via API
SB
Smartsheet
Read / Write
Connected via API
BH
BambooHR
Read / Write
Connected via API
WD
Workday
Read
Connected via API
GT
Gusto
Read
Connected via API
QB
QuickBooks
Read / Write
Connected via API
RP
Rippling
Read
Connected via API
XR
Xero
Read / Write
Connected via API
PB
PostgreSQL
Read / Write
Connected via API
IC
Intercom
Read / Write
Connected via API

If it has a REST API, Nexwatt can connect to it.

Define a custom connector with a JSON descriptor: base URL, authentication method (API key, OAuth 2.0, or bearer token), and the endpoints your agent should call. Nexwatt handles the request lifecycle, response parsing, and retry logic. Credentials are stored in the vault, never in the agent definition.

Webhook triggers are supported for any system that can make an outbound HTTP request. If your internal tool can POST a JSON payload, it can trigger an agent.

View connector documentation
JSON
{
 "connector_id": "my-internal-api",
 "base_url": "https://api.yourco.com/v1",
 "auth": {
  "type": "bearer",
  "secret_ref": "vault://nexwatt/my-api-key"
 },
 "endpoints": [
  {
   "id": "get_order",
   "method": "GET",
   "path": "/orders/{order_id}"
  },
  {
   "id": "update_status",
   "method": "PATCH",
   "path": "/orders/{order_id}/status"
  }
 ]
}

Don't see your tool? Tell us what you need.

We prioritize new connectors based on request volume. If five or more teams need the same tool, it goes to the front of the build queue. If your tool has a REST API and you can't wait, the custom connector path takes most engineering teams under an hour.