What the Vertiqa connection can do in ChatGPT or Claude
The CRM, project, document, and Conversion Page areas the Vertiqa MCP connection covers, what it can change, what stays read-only, and how to keep it inside the access you intend.
Once Vertiqa is connected, your assistant has around 136 Vertiqa tools available. You never call them by name — you ask for an outcome, and the assistant picks the tools. This article is the map of what is behind that, so you know what to ask for and where the edges are.
The fastest way to see the current list from inside a chat is to ask:
Using Vertiqa, describe your capabilities. List the entity areas you can read
and the ones you can change. Do not change anything.That runs Vertiqa's own capability description, so it always reflects what the connection can do today rather than what this page said when it was written.
What the connection covers
| Area | Read | Create and change |
|---|---|---|
| Accounts, contacts, locations | List, search, open a full record | Create, update, delete |
| Opportunities and pipelines | List and filter by pipeline, stage, and status; deal-velocity analytics | Create, update, move stage, mark won/lost/reopen, bulk import |
| Activities, notes, timeline | Activity log, notes, and the full timeline for a record | Log an activity, write or pin a note |
| Tags | List tags and an entity's tags | Create, rename, delete, tag and untag records |
| Projects and tasks | Projects, sections, tasks, statuses, checklists, comments, dependencies, work logs | Create and update all of them, plus bulk task edits |
| Cycles and modules | Cycles, burndown, modules, work item types | Create and run cycles, assign tasks to them |
| Project intake | Intake requests | Create, accept, decline |
| Documents | Search and list documents, get a download link | Upload, update, delete |
| Knowledge base | Search your organization's published articles | — |
| Conversion Pages | Page inventory, views, submissions, conversion rate, source and step performance | — |
| Analytics | Opportunity, project, portfolio, and cycle-burndown analytics | — |
Areas Vertiqa has in the app but not in the MCP connection today: scheduling and meetings, events, goals, HR, staffing, commercial estimates and invoices, business cards, workflows, and agent runs. Ask for those in Vertiqa itself or through the in-app Assistant.
Which organization it acts in
Every call happens inside one Vertiqa organization. If you belong to exactly one, the assistant uses it automatically. If you belong to more than one, the first tool call stops with a message asking for an organization, and the assistant should then list your organizations and ask which one you mean. Name the organization in your first message to skip that round trip.
What it can reach, and what to restrict
Access is scoped to organizations you are a member of — the connection cannot reach another tenant's records, and Vertiqa rejects a request for an organization you do not belong to.
Within an organization the connection is org-scoped rather than role-scoped: for the entity areas listed above, it works across the organization's records rather than a narrower slice. Treat connecting Vertiqa the way you would treat granting broad CRM and project access, and use your assistant's own per-tool controls to narrow it:
- Claude — open Customize > Connectors > Vertiqa and set Tool permissions. Each tool can be set to always allow, ask every time, or never. Setting the create, update, delete, and bulk tools to ask or never gives you a read-only connection.
- ChatGPT — a workspace admin approves an app's actions when it is published, and confirmation prompts appear before write actions in a chat.
Anything you do not want an assistant to do unattended belongs on ask every time, not on always allow.
What gets recorded
Records created or changed through the connection are ordinary Vertiqa records. They are attributed to your Vertiqa user, they appear on the record and in its timeline, and everyone in the organization sees them the same way they see work done in the app.
Vertiqa also keeps an internal log of every tool call — which tool, which organization, whether it succeeded, and how long it took. Customer content and personal details in the arguments are redacted before that log is written, and responses are limited to a fixed set of fields per record type.
Limits worth knowing
- Conversion Pages are read-only. Ask for performance and inventory; edit content, routing, and publish state in Vertiqa.
- Lists are paged. Ask for the size you want ("the top 25") or the assistant will use a default and may need to page for the rest.
- Bulk deal import is capped at 50 records per call and skips records whose external ID already exists, so a re-run does not duplicate them.
- Accounts are created one at a time. For a long list, use Vertiqa's CRM import instead.
- A deal created through the connection links to a contact, not an account. Set the account on the deal in Vertiqa, or create the contact against the account first.
- Account type is
residential,commercial, orhousehold— it is not a lifecycle label, so "prospect" or "customer" is rejected.