> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tagada.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Examples

> Real diagnostic prompts for AI agents using the TagadaPay CRM MCP

# Examples

Sample prompts you can give an AI agent connected to `@tagadapay/crm-mcp`. The agent calls the right read tools and answers with real data from your account.

<Note>
  This MCP is read-only. To act on what the agent finds, head to the in-app **Auto-fix agent** (chat widget on `app.tagadapay.com`) — it proposes fixes you approve with one click.
</Note>

## Health check

### "Show me my payment processors"

> "What payment processors do I have configured?"

The agent calls `processors.list` and answers:

```
You have 2 processors configured:
  • Stripe US (proc_a1b2) — active, currencies USD/CAD, countries US/CA
  • Adyen EU (proc_x9y8) — active, currencies EUR/GBP, countries IE/FR/DE
```

### "Are any of my domains broken?"

> "Are all my custom domains verified and pointing the right way?"

The agent calls `domains.list` (and `domains.getDnsLookup` for any unverified ones):

```
3 of 4 domains look healthy:
  ✓ checkout.merchant.com — verified
  ✓ pay.merchant.com — verified
  ✓ shop.merchant.com — verified
  ✗ legacy.merchant.com — NOT verified
        → DNS lookup: missing CNAME to proxy.tagada.io
```

***

## Diagnosing payment problems

### "Why are my payments declining?"

> "Customers are telling me their cards keep getting declined. Can you figure out what's wrong?"

The agent will:

1. `processors.list` — checks if any processors are inactive or missing currencies
2. `stores.list` → pick the relevant store
3. `funnels.list` for that store — checks default currency vs processor currencies
4. Reports back with a diagnosis

Typical answer:

```
Your only USD-capable processor (Stripe US) is currently
INACTIVE. That's why USD-denominated checkouts are failing —
there's no gateway to route them to.

To re-enable it, open the Auto-fix agent in the dashboard
and ask "re-enable Stripe US". You'll see an inline approval
card and one click puts it back in service.
```

### "Show me my recent orders for this store"

> "List the last 25 orders on store\_xxx."

```
Calling orders.list(storeId="store_xxx", pageSize=25)…

Most recent orders:
  • ord_aaa  $79.00 USD  paid       2026-04-25 21:14
  • ord_bbb  $79.00 USD  refunded   2026-04-25 21:08
  • ord_ccc  €69.00 EUR  pending    2026-04-25 21:01
  …
```

***

## Webhooks

### "My CRM isn't getting orders"

> "Klaviyo isn't receiving any new orders since this morning. What's going on?"

The agent will:

1. `stores.list` → identify the relevant store
2. `webhooks.list` for that store → find the Klaviyo endpoint
3. Report back

Typical answer:

```
Found your Klaviyo endpoint on store str_xyz:
  • we_1 → https://klaviyo.example/hook (enabled, 4 event types subscribed)

The endpoint is configured. If deliveries aren't landing,
two things to check next:
  1. Klaviyo's API key on their side (rotated tokens are #1 cause).
  2. The dashboard "Webhook deliveries" view for HTTP error codes.

I can't see delivery history from this MCP — open the
Webhooks tab in the dashboard for that.
```

***

## Funnels

### "Walk me through this funnel"

> "What does funnel fnl\_abc actually look like? Steps, currency, upsells?"

The agent calls `funnels.retrieve(funnelId="fnl_abc")`:

```
Funnel "Lead Magnet → Tripwire → Upsell"
  • storeId: store_xyz
  • baseCurrency: USD
  • status: published
  • steps:
      1. lead-form           → /go
      2. tripwire-checkout   → /pay   ($9 trial)
      3. one-click-upsell    → /add   ($79 main)
      4. thank-you           → /done

Looks well-formed; no missing steps.
```

***

## Customers

### "Find customer by email"

> "Pull up the account for [ana@example.com](mailto:ana@example.com)"

The agent calls `customers.list(email="ana@example.com")`:

```
1 customer match:
  • cus_a1b2  Ana Soto   ana@example.com
              first order 2025-11-04, last order 2026-04-19
```

Then `customers.retrieve(customerId="cus_a1b2")` for full detail.

***

## Composing with other tools

### Pair with the [Node SDK](/developer-tools/node-sdk/quick-start)

If you want the AI agent to **act** on what it diagnosed (mutate stores, create funnels, charge customers), connect the `@tagadapay/node-sdk` as a separate tool. The Node SDK has full write access; the CRM MCP gives a fast read surface.

### Pair with [Studio MCP](/developer-tools/studio-mcp/introduction)

Use the CRM MCP for "what is configured" and Studio MCP for "edit my landing pages". Together they cover diagnosis + creative work.

***

## What this MCP can't help with

These prompts will fail (gracefully) — there's no tool for them in v1:

* ❌ "Refund order #1234" — write operation; use the Node SDK
* ❌ "Enable my Stripe processor" — write operation; use the in-app Auto-fix agent
* ❌ "Replay this webhook" — write operation; use the dashboard or Node SDK
* ❌ "What's the average customer LTV?" — analytics not exposed; use the dashboard or BigQuery export

The agent will tell you which surface to use instead.