Connector catalog

Give your agent the tools to finish the job.

Install a provider once and Ayooda adds its supported read and write actions together. Write actions stay opt-in, require explicit customer confirmation, and can be tested before going live.

Shopify

E-commerce

Order lookup, payment transactions, and customer-notifying refunds.

3 actions included

Stripe

Payments

Customer lookup and confirmed email updates.

2 actions included

HubSpot

CRM

Contact lookup and confirmed email updates.

2 actions included

Zendesk

Support

Ticket lookup plus public resolution and solve actions.

2 actions included

Notion

Knowledge

Search pages and databases shared with your integration.

1 action included

Linear

Support

Look up issues by identifier with status and priority context.

1 action included

Intercom

CRM

Find customer contacts and account context by email.

1 action included

Zapier

Automation

Trigger a Catch Hook with structured customer-support events.

1 action included

Custom REST API

Custom

Define guarded read or write actions for any public HTTPS JSON API, with encrypted bearer or header credentials.

GET · POST · PUT · PATCH · DELETE

Model Context Protocol

MCP

Connect Streamable HTTP or SSE MCP servers and expose their discovered tools to a specific Ayooda agent.

Bearer · custom header · no auth

How connections stay controlled

  1. Scoped per agentEach agent receives only the tools you connect to it.
  2. Secrets stay server-sideCredentials are encrypted at rest and removed from every API response.
  3. Writes are explicitWrite tools are disabled by default and their descriptions require confirmation before execution.
  4. Test before deploymentUse the agent sandbox to exercise connected tools without adding test traffic to customer analytics.

Connect your first provider

Create an agent, open its Tools tab, and install a complete provider bundle in one guided flow.

Create an agent