Use Yuno with AI assistants

Connect your Yuno account to the AI assistant you already use. Analyze your payments data, search the Yuno API documentation, and operate payments on the Yuno accounts you have access to, all in plain language. You sign in with your Yuno user, so the assistant only sees and acts on what your user and organization are allowed to.

​

Setup

​

Accounts

Payment actions run on one of your Yuno accounts. By default, the connector uses your principal account: the one set as default for your Yuno user in the dashboard, or the first account you have access to otherwise.

• Ask “Which Yuno accounts can I use?” to list the accounts available to you and see which one is the default.
• Tell the assistant which account to use for a given request (for example, “use account <account>”) to switch away from the default.
• Accounts you don’t have access to are rejected: the connector can only use accounts your Yuno user is entitled to.

​

Safety model

• Analytics is read-only: SQL statements that modify data or schema are always rejected.
• Payment tools can write: they can create and modify data. Depending on your Claude or ChatGPT settings, the assistant may ask for your approval before running them.
• Production confirmation: on production, cancellations, refunds, and deletions return a preview first and only run after the assistant confirms within 5 minutes.
• Permissions come from your Yuno user’s access and organization, not from the assistant: it can only do what your account is already allowed to do.

​

What you can do

The connector exposes tools across four capability groups: analytics, Yuno API documentation, accounts, and payments. The assistant chooses the right tool automatically, so you never have to call them by name, but knowing what’s available helps you know what to ask.

​

Analytics (read-only SQL)

​

Yuno API documentation

​

Accounts

​

Payments

Payment tools are prefixed pay__ and grouped by resource below. The assistant can fetch any payment tool’s full parameters itself through pay__describeTool, so this page groups tools by resource instead of listing every parameter. Read = no changes. Write = creates or updates data. Destructive = cancels, refunds, or deletes; requires confirmation on production.

​

Ask in plain language

• “What was my payment approval rate by payment method over the last 30 days?”
• “Show transaction volume by country for July, and flag any country that dropped more than 10% vs June.”
• “What are my top 5 decline reasons this month, and which provider do they come from?”
• “Compare conversion between credit card and PIX in Brazil this quarter.”
• “Describe the transactions table and show me a few sample rows.”
• “Build me a weekly summary: volume, approval rate, refund rate, and average ticket.”
• “How do I create a payment with 3DS?”
• “Which Yuno accounts can I use?”
• “Refund payment <payment_id>.”
• “Create a payment link for 50 USD.”

​

Scoped to your account

• Scoped to your account: The connector authenticates with your Yuno credentials and can only see and act on the accounts your user is entitled to. See Safety model for how read-only analytics and payment writes are kept safe.
• Query limits: Very large result sets are truncated rather than streamed in full, and sessions are rate-limited to keep the warehouse healthy. For bulk exports, use the Yuno dashboard or API.
• Partial outages: If one capability (analytics, documentation, or payments) is temporarily unavailable, only its tools disappear; the rest keep working.

​

Troubleshooting

Claude says the Yuno connector is disconnected Go to Settings → Connectors, find Yuno, and click Reconnect, then re-authorize. If the connector doesn’t appear in a chat, check that it’s enabled in the chat’s search & tools menu. ChatGPT doesn’t call the Yuno app Invoke it explicitly by typing @Yuno at the start of your message, or mention “using Yuno” in the prompt. If it’s still unavailable, remove and re-add the app from its directory listing. Queries fail with a “no database selected” error Ask the assistant to qualify tables with their database name (for example analytics.transactions) or to state which database to use. Asking “what tables are available?” first usually resolves this. Results look truncated That’s expected for large outputs. Ask the assistant to aggregate (totals, top-N, grouped summaries) instead of listing raw rows, or narrow the date range. The assistant used the wrong account Ask “Which Yuno accounts can I use?” and tell it which one to use for the request. “Confirmation expired” Production confirmations last 5 minutes. Ask the assistant to repeat the action to get a fresh confirmation. “Connect” or “consent required” message The assistant is asking you to (re)authorize the Yuno connector: your session or a prior consent has expired or wasn’t completed. Go through the connect step again (see Setup above) and retry your request.

​

FAQ