Home / Product / Integrations
Integrations

Keep your helpdesk.We plug in. You migrate nothing.

Your team keeps working where it works. Pronomy reads tickets from your helpdesk and acts in your billing, store and CRM through their APIs. Connect your existing tools through native integrations, APIs, webhooks and MCP.

Stays yoursYour helpdeskZendesk, or anything with an API
WebhookREST APIMCP
Does the workPronomyChecks, acts in billing, store, CRM, then replies
Before we connect

Access is not one switch.

For each flow, we agree what the agent can read, what it may change and what needs a person. A tool name in a list is not permission to use every feature.

Access checklist for a proposed integration
AccessExampleConfirm before rollout
ReadTickets, account details, charges or order state.Which records are needed, how identity is verified, and which endpoint provides them.
ChangeReply to a ticket, refund a charge, update an order.The exact action, required permission and reliable confirmation of its result.
Ask a humanAn exception, a disputed charge or an action above the agreed limit.Who approves, where the request goes, and what context follows it.

Examples, not a list of granted permissions. Zendesk, Intercom and Slack have native integrations. Other connections depend on the available interfaces and the flow we configure with you. See a refund workflow →

Three ways in

Webhook. API. MCP.Pick whatever your stack already speaks.

These are connection methods, not a guarantee that every action is available. We check the endpoints, permissions and result handling for your flow before rollout.

Webhook

Your helpdesk sends us an event when a ticket arrives or changes. We run the flow and answer back through your helpdesk's API.

Best for: getting tickets in from any helpdesk or form.

// example payload, illustrative
{
  "event": "ticket.created",
  "ticket_id": "48213",
  "channel": "email",
  "customer": { "email": "jane@example.com" },
  "message": "I cancelled and still got charged."
}
REST API

You describe the endpoints the agent may call: refund, cancel, change plan, update an order. Each one gets its own permission and autonomy level.

Best for: taking real actions in billing, commerce and your own backend.

# action definition, illustrative
name:     refund_charge
method:   POST
url:      https://billing.example.com/refunds
input:    charge_id, amount
success:  status == "succeeded"
autonomy: 4 up to $50, 3 above
MCP

If a system already runs an MCP server, point Pronomy at it. Its tools show up as actions, and you allow or block each one.

Best for: internal tools and anything that already has an MCP server.

// generic MCP config, illustrative
{
  "mcpServers": {
    "orders": {
      "url": "https://mcp.example.com/orders",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Snippets are illustrative, not our API reference. Field names and URLs are examples. We share the real setup details during onboarding.

What connects

Your tools. Connected.Helpdesk, billing, knowledge and your own systems.

"Native" means a dedicated integration. Other systems require a connection through their own interfaces. The actions available depend on your plan, permissions and the endpoints the system exposes.

Plain keyword match on the names below.
NativeVia API / webhook / MCP

Helpdesks where tickets live

ZendeskNative
IntercomNative
FreshdeskVia API / webhook / MCP
GorgiasVia API / webhook / MCP
Help ScoutVia API / webhook / MCP
HubSpotVia API / webhook / MCP
FrontVia API / webhook / MCP
Salesforce Service CloudVia API / webhook / MCP

Billing & commerce where actions happen

StripeVia API / webhook / MCP
ShopifyVia API / webhook / MCP
RechargeVia API / webhook / MCP
ChargebeeVia API / webhook / MCP
PaddleVia API / webhook / MCP
RevenueCatVia API / webhook / MCP
WooCommerceVia API / webhook / MCP
Your own backendVia API / webhook / MCP

Knowledge what the agent reads

NotionVia API / webhook / MCP
ConfluenceVia API / webhook / MCP
Google DriveVia API / webhook / MCP
MongoDBVia API / webhook / MCP

Chat & internal where your team talks

SlackNative
Microsoft TeamsVia API / webhook / MCP
DiscordVia API / webhook / MCP
TelegramVia API / webhook / MCP

Product names are trademarks of their owners. Non-native listings identify systems to assess through their interfaces, not prebuilt connectors or guaranteed support for every action. No partnership or endorsement is implied.

Knowledge sources

It reads what your team reads.And it tells you where the docs are thin.

Answers come from your sources, not from the open internet. When a question has no good source, the agent says so and hands off. It would rather fetch a person than invent a refund policy. With Analytics, those gaps become a list of docs to write.

  • Website URLsHelp center, FAQ, pricing and policy pages
  • Static documentsPolicies, playbooks and internal guides you upload
  • Predefined responsesYour macros and approved wording, used as-is when required
  • Past conversationsHow your best agents actually solved it
  • Notion · ConfluenceInternal wikis where the real rules live
  • Google DriveDocs and sheets your team keeps up to date
  • MongoDBStructured product data, such as plans and feature flags
Morrow shipping, returns, membership and saved-answer sources, with each source explicitly marked Not indexed.
Your knowledge, in one place

Morrow Club demo workspace. These four sources are present, but have not been indexed.

Website widget

No helpdesk yet?Put the agent on your site.

Add Pronomy as a chat widget on your website. Same flows, same actions, same scorecards. When a conversation needs a person, it goes to your team (in Slack, for example) with the full story.

  • Says it's an AI assistant, clearly, from the first message
  • Replies in the customer's language
  • A human is always one message away
your-store.example
HelpAI assistant
YouWhere's my order? It's been a week.
AI assistantFound it. It left the warehouse on Monday and the carrier shows delivery tomorrow. Want the tracking link?
What setup actually takes

The connector is the easy part.Your rules deserve more attention.

The connection
Minutes

Often that's all it takes to connect a helpdesk or an API. You can do it yourself, or we do it for you, free.

The rules

Takes longer. Here's why.

  1. Your policies live in people's heads. "We refund within 14 days" usually comes with five unwritten exceptions.
  2. Permissions are real decisions. Which refunds can the AI do alone? Which need a person? You decide that, not us.
  3. "Correct" needs a definition. Scorecards can only grade what you've written down.
  4. Trust is earned. Shadow mode first, then one live flow, then more.

So we don't hand you an empty form. We read your tickets, docs and policies and pre-fill a draft of your flows for you to confirm. Onboarding is free.

Security & data

Data and access commitments.

  • DPA available before we touch any data
  • Your customer data is never used to train models
  • Role-based access, human approval for risky actions, full audit log

Read exactly what we do with your data →

Straight answers

Questions worth asking.Before another system gets access.

Do we have to switch helpdesks?
No. Your team keeps its helpdesk, its macros and its views. Pronomy works inside it. If you don't have a helpdesk, you can start with the website widget.
What's the difference between "native" and "via API"?
Native (Zendesk, Intercom and Slack) means we built and run a dedicated integration. Via API, webhook or MCP means we connect through the tool's own interfaces. Both run the same flows. Native is just less setup.
Who does the technical setup?
Whoever you prefer. If your team has the required access, they can connect it; otherwise we do it with you during onboarding at no charge. Timing depends on the systems and permissions involved.
Will this mess with the setup we already have?
No. Your macros, views and routing stay as they are. Pronomy reads and writes through your tools' APIs, with only the permissions you give it. Start in shadow mode and it writes internal notes without sending anything to a customer, so you can watch before you trust it.
Can the agent act in our own internal admin panel?
Yes, if it has an API or an MCP server. You define each action the agent may call and set its autonomy level, from "suggest only" to "do it alone inside this flow".
What happens if one of our systems is down?
The action fails, and the agent knows it failed. It doesn't tell the customer "done". Depending on your flow, it retries or hands off to your team with a note. The audit log shows exactly what happened.
Which channels do you cover?
Whatever arrives through your helpdesk (email, chat, forms), Slack, and our website widget. We don't offer a voice channel.
P.S.

If part of your stack is a webhook nobody wants to touch, send us the documentation. I’ll tell you honestly whether we can plug in and what the setup would take.

Name the tool.We’ll tell you how it connects — or that it doesn’t.