Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Your CRM + project pipeline, on call to Claude
Cohesive360 exposes your C360 Business Suite tenant to Claude through 103 purpose-built tools across 9 capability areas. CRM contacts and companies, project + task CRUD, tenant schema discovery, segmentation (Worlds + Circles), Office suite (Proposals + Contracts), Forms + Automation (full CRUD), and portal-only dashboard views. Covers both the API surface AND the portal-rendered data the REST endpoints don't expose.
CRM, project pipeline, segmentation — one connector
Contacts, companies, projects, dashboard, Worlds and Circles all answer to plain English. Claude can pull a contact's full project history or push a quick segmentation change without you leaving chat.
Tenant-isolated by design
Every read and write is scoped to your tenant by the API key. Multi-tenant operators (consultancies, fractional ops teams) connect each tenant separately so accounts, projects, and Worlds never bleed across.
Schema-aware writes
Before writing custom fields, Claude reads the tenant's schema (allowed industries, picklist values, field UUIDs). Prevents the 'writes succeeded but the value isn't there' failure mode that comes from guessing field shapes.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
3 workflow areas in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
1.63.0 added Office-suite reads — proposals, contracts, invoice/estimate templates (recurring, accumulating, on-demand), portal pages, public landing pages.
1.63.0 added Office-suite reads — proposals, contracts, invoice/estimate templates (recurring, accumulating, on-demand), portal pages, public landing pages.
What you can ask Claude
- “List our proposals from this month”
- “Show me active contracts”
- “What recurring invoice profiles do we have”
- “List on-demand estimate templates”
Underlying tools (7)
list_proposalslist_contractslist_recurring_invoice_profileslist_accumulating_invoice_profileslist_on_demand_estimate_templateslist_proposal_templates_fulllist_proposal_page_templatesFull Forms CRUD (create / read / update / delete / duplicate / publish-config / schema parse / definition save) and Automation deep-dive (templates, trigger conditions, action catalog, trigger vocabulary). 1.63.0 introduced 24 tools across these surfaces.
Full Forms CRUD (create / read / update / delete / duplicate / publish-config / schema parse / definition save) and Automation deep-dive (templates, trigger conditions, action catalog, trigger vocabulary). 1.63.0 introduced 24 tools across these surfaces.
What you can ask Claude
- “List our forms”
- “Get the schema of form 12345 and show me the field definitions”
- “Create a new Kickoff form”
- “List automation templates and their configured actions”
- “What action types are available for Staff-target automations”
Underlying tools (22)
list_formscreate_form_webduplicate_form_webdelete_form_webget_form_publish_configget_form_schemasave_form_definitionlist_form_submissionsget_form_submissionlist_form_templateslist_form_themessave_form_as_templateget_staff_submit_formlist_automation_templatesget_automation_template_configget_automation_template_triggersget_automation_action_catalogget_automation_trigger_catalogdelete_automation_templatelist_flowslist_scheduleslist_checklistsRead data that lives only in the logged-in C360 portal — project tasks, project leaders, contact-scoped task/project tabs, dashboards, files, timers, work requests, teams, custom dashboards. Backed by the connector's web-session emulation when the API doesn't expose a clean endpoint.
Read data that lives only in the logged-in C360 portal — project tasks, project leaders, contact-scoped task/project tabs, dashboards, files, timers, work requests, teams, custom dashboards. Backed by the connector's web-session emulation when the API doesn't expose a clean endpoint.
What you can ask Claude
- “What's on my C360 dashboard this morning”
- “Who's the leader on the Acme Onboarding project”
- “List the tasks tied to contact 12345”
- “Show me all the projects on Jane Doe's contact card”
- “List timers running across the firm”
- “What work requests are open”
Underlying tools (30)
get_dashboard_summaryget_project_leaderlist_contact_projects_weblist_contact_tasks_weblist_filessearch_filesresolve_file_targetdownload_fileupload_filecreate_folderrename_filedelete_filelist_timerslist_work_requestslist_teamslist_users_stafflist_announcementslist_custom_dashboardslist_content_stackslist_portal_pageslist_public_landing_pageslist_popup_noticeslist_friendly_slugslist_activity_eventslist_import_logslist_calendar_eventslist_project_generatorslist_pm_project_templatesc360_web_fetch_html_summaryc360_web_inspect_pageLimits and roadmap
What the C360 Business Suiteconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Worlds / Circle administration. Creating new Worlds, editing the Power-up taxonomy, and changing circle membership policies are admin-only in C360. We read the segments and members but don't modify the taxonomy.
- Marketing campaign sends. Subscribing a contact to marketing is supported; triggering a campaign send is not. Use C360's Campaigns workflow for the actual send.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Office billing (invoices, payments, gateways). Invoices, Estimates, Expenses, Subscriptions, and Payments are SPA-only in C360 today (`?ajax=X-grid` returns HTML). Surface awaits AJAX-endpoint discovery — folded into a future ship.
- CRM Follow-Ups, Deals; LMS Products/Courses; Inbox; Workspaces. These remain SPA-only on the C360 portal. Tools land when we capture the XHR shape from DevTools.
- Custom-report execution. Per-tenant custom reports need careful UX before chat exposure. Use C360's reports surface.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Per-tenant credential isolation
API key + portal-session credentials are stored per-user, per-tenant, AES-256-GCM-encrypted, master key in Azure Key Vault. Multi-tenant operators can connect more than one C360 tenant and switch between them; credentials never bleed across.
Two-credential model — different blast radius
The API key authorises structured CRM reads/writes. The portal session unlocks dashboard + project-task views the REST API doesn't expose. Rotating either invalidates only that surface, not both.
Schema-aware before-write
Custom-field writes (industry, picklist values, project status) verify against the tenant's schema first. Bad picklist values fail loudly with the allowed-values list, not silently no-op.
Web-session auto-renewal
When the cached portal session expires or C360 invalidates it, the connector re-logs once and retries the request transparently. After two failed renewals in a row the connector stops trying and surfaces the error so credentials can be checked.
Write-with-review on segmentation + marketing
Adding a contact to a marketing audience or a Worlds segment changes who gets ongoing outreach — Claude drafts these as previewable changes you confirm before they commit.
What C360 Business Suite via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your C360 Business Suitetenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.