Resources

Integrations Directory

Everything Katexs connects to out of the box, what each connection can do, and what to reach for when the thing you need is not on the list.

How connections work

Connect an integration once in Settings → Integrations and it becomes available as a set of typed tools any agent can use. Credentials are stored encrypted per workspace, which is why sandbox and production environments each need their own connection.

Scheduling

Integration	Auth	Tools exposed
Google Calendar	OAuth	find_availability, create_event, reschedule_event, cancel_event
Microsoft 365 / Outlook	OAuth	find_availability, create_event, cancel_event
Calendly	API key	list_event_types, create_scheduled_event

Availability lookups respect the calendar's own busy blocks plus any buffer you configure in the tool settings. Set the buffer once rather than teaching the prompt to add travel time.

CRM and pipeline

Integration	Auth	Tools exposed
GoHighLevel	OAuth	upsert_contact, add_note, move_opportunity, trigger_workflow
HubSpot	OAuth	search_contact, upsert_contact, create_deal, log_engagement
Salesforce	OAuth (JWT bearer supported)	soql_query, upsert_lead, create_task, update_opportunity
Pipedrive	API key	search_person, create_deal, add_activity

Salesforce and HubSpot connections honour field-level permissions on the connected user. Create a dedicated integration user with exactly the objects your agents need rather than connecting an admin account.

Telephony and messaging

Integration	Auth	Use
Twilio	Account SID + auth token	Import numbers, SMS/MMS, carrier failover
SIP trunk	Credentials or IP allowlist	Bring an existing carrier or PBX
Slack	OAuth	Post call summaries, escalation alerts, approval prompts

Automation platforms

Integration	Direction	Notes
n8n	Both	Native Katexs node; trigger on call.ended, call the API to place calls
Zapier	Both	Triggers for call and session events, actions for calls and contacts
Make	Both	Webhook trigger plus HTTP modules against the REST API

Automation platforms are the right answer when the logic belongs to your operations team rather than your agent. Keep the agent focused on the conversation and let n8n or Zapier fan the outcome out to five systems.

json

{
  "event": "call.ended",
  "call_id": "call_9a2f01",
  "agent_id": "agt_7d11c9",
  "outcome": "booked",
  "duration_seconds": 137,
  "variables": {
    "caller_name": "Dana Whitfield",
    "appointment_id": "apt_8f2c41"
  },
  "recording_url": "https://api.katexs.com/v1/recordings/call_9a2f01",
  "transcript_url": "https://api.katexs.com/v1/transcripts/call_9a2f01"
}

When it is not on the list

Custom tool — Any HTTPS endpoint with a JSON schema becomes a tool the agent can call. This covers most in-house systems.
Outbound webhook — Push call and session events to your own service and do the integration on your side.
REST API — Place calls, manage agents, and read logs programmatically.

Configure integrations Webhook events