Connector catalogue
Connectors attach to one agent, so a public storefront agent and an internal one never share access. Connect the same service to two agents and each holds its own credential.
Commerce
Catalogue, carts and store policies.
Shopify
Nothing to enterSearch the catalogue, build a cart and answer questions about returns and shipping.
WooCommerce
Paste a keySearch the product catalogue of a WooCommerce store.
Wix
Sign inRead catalogue and store data from a Wix site.
Salesforce Commerce Cloud
Paste a keyShopper APIs for catalogue and cart on a B2C Commerce storefront.
Payments
Charges, refunds and billing history.
Stripe
Sign inLook up payments, customers and subscriptions.
PayPal
Sign inLook up transactions and orders.
Knowledge
Documents, records and published content.
Notion
Sign inSearch pages and databases so the agent answers from your own documentation.
Airtable
Sign inRead records and schema from your bases.
Webflow
Sign inRead sites, collections and CMS items.
Work tracking
Issues, tasks and projects.
Linear
Sign inRead issues so a conversation can become tracked work.
monday.com
Sign inRead boards and items.
Engineering
Errors, data and infrastructure.
Sentry
Sign inRead issues and events for an agent working on an internal platform.
Supabase
Sign inRead projects, database schema and analytics.
Cloudflare
Sign inRead logs and analytics to answer questions about traffic and errors.
Automation
Reach tools that have no connector of their own.
Zapier
Sign inRun the Zaps you expose, reaching tools with no connector of their own.
How connectors authenticate
What a service asks of you depends on how that service publishes access.
| Kind | What you do |
|---|---|
| Nothing to enter | The store already publishes what an agent needs. Type the address and it is connected. |
| Sign in | You are sent to the service, you approve the access, and you land back here. Duvi never sees your password. |
| Paste a key | You create a credential in the service and paste it in. It is encrypted and never shown again. |
Shopify asks for nothing at all. Every Shopify store already publishes a shopping interface, so the storefront address is the whole setup.
Connect a service
Open the agent
Go to the agent, then Integrations.
Pick the service
The catalogue is grouped by what each service is for. Selecting one opens the provider page with its description, available tools and connection form.
Approve the access
For a sign-in connector, the service takes you through its own approval screen and returns you to the same page. Duvi never sees your password.
Choose the tools
Duvi asks the service what it can do and lists the tools it found. Turn off any tool you would rather the agent never called.
Read-only access
Connectors request read access wherever the service separates reads from writes. Duvi connects Linear with read, Sentry with org:read, and Airtable with record and schema reads. An agent answering a customer has no reason to delete a repository or refund a payment.
Where a service offers no read-only grant, Duvi limits which of its tools an agent may call instead. The catalogue lists what each tool does before you connect it.
Connection states
Each connection carries one of three states. A connection that is not working shows the reason at the top of its panel, and the agent carries on without it rather than failing the conversation.
| State | What it means |
|---|---|
| Connecting | Set up, but the service has not confirmed yet. Give it a moment. |
| Connected | Working. Its enabled tools are available to the agent. |
| Not working | Usually access withdrawn or expired at the service. Reconnect from the same panel. |
Two states look like faults and are not:
| What you see | What it means |
|---|---|
| Connected, no tools listed | The service answered and offered nothing. Usually a feature that still needs switching on at that service. |
| Tools listed but never called | The agent had no reason to call one. Ask it something only that service could answer. |
For HTTP actions and MCP servers you host yourself, see Tools.