Skip to content
NewPazau Agent 3 is here: Procedures that test themselves before they go live
Integrations

Plugged into the systems that run your business.

120+ prebuilt connectors for the CRMs, reservation systems, EHRs, claims platforms, and payment processors your support team already depends on. Anything else with an API becomes an Action in an afternoon.

120+ prebuilt connectorsOpenAPI importScoped OAuth credentialsPer-Action spend limits
S
A
E
G
S
S
T
S
P
Action runtime
120+
prebuilt connectors across 12 categories
900+
prebuilt Actions: read, write, and approve
11 min
median time to import an OpenAPI spec and run a first Action
0
credentials exposed to the model. Secrets stay in the vault.
Directory

The most-deployed connectors.

A selection of 44 of our 120+ connectors across 12 categories. Every connector ships with typed Actions, scoped permissions, and Trace logging.

44 integrations
  • SActions
    Salesforce
    CRM

    Read accounts and cases, write case updates, and log every AI resolution as an activity.

  • HSync
    HubSpot
    CRM

    Sync contacts and deal stage so Pazau Agent knows who is a VIP before the first reply.

  • MDActions
    Microsoft Dynamics 365
    CRM

    Customer 360 in the Inbox sidebar, plus case create and update Actions.

  • ZChannel
    Zendesk
    Helpdesk

    Run Pazau Agent on Zendesk tickets without migrating. Handoffs land in your existing views.

  • SActions
    ServiceNow
    Helpdesk

    Open and update CSM cases, and attach the full Trace to every handoff.

  • FChannel
    Freshdesk
    Helpdesk

    Bring Freshdesk tickets into Pazau, or run Agent in place and sync status back.

  • SSChannel
    Salesforce Service Cloud
    Helpdesk

    Agent resolves in Service Cloud; unresolved cases route with summary and next step.

  • SActions
    Shopify
    Commerce

    Order lookup, address edits, returns, refunds, and discount codes, within limits you set.

  • SCActions
    Salesforce Commerce Cloud
    Commerce

    Order status, cancellations, and appeasements for enterprise storefronts.

  • BActions
    BigCommerce
    Commerce

    Order and customer lookups, returns, and store credit.

  • LRActions
    Loop Returns
    Commerce

    Start exchanges and returns in-conversation, with label generation.

  • NActions
    Narvar
    Commerce

    Carrier-level tracking and delivery promises for WISMO conversations.

  • NActions
    NetSuite
    Commerce

    Sales orders, RMAs, and invoice status from your ERP.

  • AActions
    Amadeus
    Travel & PSS

    PNR retrieve, reshop, rebook, and ticket reissue on Altéa and GDS content.

  • SActions
    Sabre
    Travel & PSS

    Booking lookup, schedule-change handling, and exchanges via Sabre APIs.

  • NActions
    Navitaire
    Travel & PSS

    Rebooking and ancillaries for low-cost carrier reservation systems.

  • OOActions
    Oracle OPERA Cloud
    Travel & PSS

    Reservation changes, room upgrades, and folio lookups for hotels.

  • EActions
    Epic
    Healthcare & EHR

    Scheduling, referrals, and MyChart account help over FHIR R4, under a BAA.

  • OHActions
    Oracle Health (Cerner)
    Healthcare & EHR

    Appointment booking and patient demographics via FHIR APIs.

  • AActions
    athenahealth
    Healthcare & EHR

    Appointments, patient balances, and refill request routing.

  • GActions
    Guidewire
    Insurance core

    FNOL intake into ClaimCenter, policy lookup in PolicyCenter, billing status.

  • DCActions
    Duck Creek
    Insurance core

    Policy servicing, endorsements, and claim status for P&C carriers.

  • MActions
    Majesco
    Insurance core

    Policy and billing inquiries for L&A and P&C lines.

  • SActions
    Stripe
    Payments

    Refunds, subscription changes, and invoice lookups with per-Action spend limits.

  • AActions
    Adyen
    Payments

    Refunds, payment status, and dispute lookups across markets.

  • BActions
    Braintree
    Payments

    Transaction search and refunds for PayPal and card payments.

  • TChannel
    Twilio
    Telephony

    Voice, SMS, and WhatsApp through your Twilio account. Keep your numbers.

  • GCChannel
    Genesys Cloud
    Telephony

    Pazau Voice as the front door, with warm transfer into Genesys queues.

  • ACChannel
    Amazon Connect
    Telephony

    Drop Pazau Voice into contact flows; transfer with attributes and transcript.

  • STChannel
    SIP trunking
    Telephony

    Bring any carrier over SIP/TLS with SRTP. No number porting required.

  • WBChannel
    WhatsApp Business
    Messaging

    Templates, rich replies, and 24-hour session handling, managed in the Inbox.

  • AMChannel
    Apple Messages for Business
    Messaging

    List pickers, Apple Pay requests, and authentication in iMessage.

  • FMChannel
    Facebook Messenger & Instagram
    Messaging

    DMs and comments from Meta surfaces in one queue.

  • GBChannel
    Google Business Messages
    Messaging

    Conversations started from Search and Maps, routed like any chat.

  • SSync
    Snowflake
    Data & Analytics

    Conversations, QA scores, and Traces delivered to your warehouse every 15 minutes.

  • BSync
    BigQuery
    Data & Analytics

    Scheduled exports of conversation and resolution tables.

  • SSync
    Segment
    Data & Analytics

    Send resolution and CSAT events; read traits to personalize replies.

  • DSync
    Databricks
    Data & Analytics

    Delta Sharing of Insights tables for your own models and BI.

  • OSSO
    Okta
    Identity

    SAML SSO and SCIM provisioning, with group-to-role mapping.

  • MESSO
    Microsoft Entra ID
    Identity

    SSO, SCIM, and conditional access for agents and admins.

  • AActions
    Auth0
    Identity

    Verify end customers in the Messenger with your existing login.

  • SActions
    Slack
    Collaboration

    Approval requests, escalations, and daily Insights digests in channels.

  • MTActions
    Microsoft Teams
    Collaboration

    Approve refunds and credits from Teams; swarm on tricky conversations.

  • JActions
    Jira
    Collaboration

    File bugs from conversations with the transcript and customer context attached.

Build your own with Actions

If it has an API, Pazau can use it.

Point Pazau at an OpenAPI spec or describe a REST endpoint. Each operation becomes a typed Action that Procedures can call, with limits and approvals you control.

  • Import OpenAPI 3.x or Postman. Pazau generates one Action per operation, with parameter schemas and descriptions.
  • Secrets never reach the model. OAuth 2.0, API keys, and mTLS live in the Pazau vault and are injected at call time.
  • Guardrails on every write. Spend limits, approval thresholds, and rate caps are set per Action, not per prompt.
  • Test before you ship. Run Actions against your sandbox and simulate Procedures on past conversations.
parcel-ops.openapi.yaml
yaml
# Your existing spec. Pazau reads it as-is.
openapi: 3.1.0
paths:
  /shipments/{tracking_id}/redeliver:
    post:
      operationId: schedule_redelivery
      summary: Book a new delivery window for a missed parcel
      x-pazau:
        effect: write          # requires confirmation from customer
        rate_limit: 5/conversation
        approval: none
      requestBody:
        required: [window_start, window_end]
Imported · 14 operations → 14 Actions · 2 flagged as writes
Terminal
bash
$ curl -X POST https://api.pazau.com/v1/actions/import \
    -H "Authorization: Bearer $PAZAU_API_KEY" \
    -F "spec=@parcel-ops.openapi.yaml" \
    -F "auth=oauth2:parcel-ops-prod" \
    -F "environment=sandbox"

{
  "imported": 14,
  "actions": ["get_shipment", "schedule_redelivery", "update_drop_location", …],
  "writes_requiring_review": ["issue_credit", "cancel_shipment"],
  "environment": "sandbox"
}
Built to the same standard

Every connector gets the controls your security team asks about.

Prebuilt or custom, every integration runs through the same Action runtime. That means one permission model, one audit trail, and one place to turn things off.

Least-privilege credentials

Connectors request only the scopes their Actions need. Read-only by default; writes are opt-in per Action.

Pazau Guard in the loop

PII is redacted from Action responses before the model sees them. Card numbers and health identifiers stay tokenized.

Limits and approvals

Cap refunds at $250, require a CX lead above that, and stop any Action after five calls in one conversation.

Typed and versioned

Action schemas are versioned with your Procedures. Roll back a connector change as easily as a copy edit.

Region-pinned execution

EU workspaces call your systems from eu-west-1 (Dublin) and eu-central-1 (Frankfurt). Data does not leave the region.

Private connectivity

Reach on-premise PSS, EHR, and core systems over AWS PrivateLink, IP allowlists, or a site-to-site VPN.

FAQ

Integration questions.

Need a connector we don't list? Email partners@pazau.com.

Explore the developer platform
Do I have to replace my helpdesk to use Pazau Agent?+
No. Pazau Agent runs on top of Zendesk, Salesforce Service Cloud, ServiceNow, and Freshdesk. It resolves what it can and hands the rest to your existing queues with a summary and the full Trace. Many customers move to Pazau Inbox later; none have to.
Are integrations included in every plan?+
All prebuilt connectors and custom Actions are included on Growth, Business, and Enterprise. Private connectivity (PrivateLink, VPN) and on-premise connectors for PSS, EHR, and insurance core systems are available on Enterprise.
How do you handle credentials?+
Credentials are encrypted with AES-256 in a dedicated vault, scoped per workspace and environment, and injected at call time. The model never sees tokens, keys, or raw secrets, and every use is logged in the Trace.
Can Actions call internal APIs that aren't on the public internet?+
Yes. Enterprise workspaces can reach internal services through AWS PrivateLink, a site-to-site VPN, or a lightweight relay you run inside your network. Calls originate from fixed IP ranges you can allowlist.
What happens when a connected system is down?+
Actions have per-call timeouts and retries with backoff. If a system stays unavailable, Procedures fall back to the path you define, usually a handoff with context, so customers aren't told something that isn't true.
Can I stream Pazau data into my warehouse?+
Yes. Snowflake, BigQuery, and Databricks connectors deliver conversations, QA scores, resolution outcomes, and Traces on a 15-minute cadence. Webhooks cover anything real-time.

Bring your stack. We'll bring the connectors.

Tell us which systems your agents touch every day. In a 30-minute call we'll map them to prebuilt connectors and Actions.