Skip to content

Generic CRM

Not on HubSpot? The generic CRM connector is a REST adapter for whatever CRM your business already runs. You supply the API base URL and a token, and the CRO gets the same pipeline, deal, contact, and activity tools it would get from a provider-specific connector.

  • Plan: any plan. Counts as one integration toward your plan’s quota.
  • An HTTPS API base URL for your CRM, for example https://api.example-crm.com/v2. Plain HTTP, redirects, and private or internal hosts are refused — requests go through the platform’s public HTTP transport with redirects disabled.
  • A bearer token or API key that can list contacts. The platform sends it as Authorization: Bearer <token> by default.
  • Your CRM must expose list endpoints for contacts, deals, and activities that return JSON arrays. Defaults: /contacts, /deals, /activities; deals are read with stage and value fields; stage changes use PATCH.
  1. Open Settings → Connectors and click + on CRM.
  2. Enter the token in Provider access token and the API root in HTTPS CRM API base URL, then click Verify and connect. The platform calls GET {base_url}/contacts?limit=1 with your token before saving; a non-2xx response saves nothing.
  3. CRM appears under Connected.

If your CRM’s paths or field names differ from the defaults, connect through the API instead of the dialog so you can pass the overrides in config:

Terminal window
curl -X POST https://app.ultimateteam.ai/api/v1/connectors/crm_generic/connect \
-H "Authorization: Bearer <owner session token>" \
-H "Content-Type: application/json" \
-d '{
"credentials": {"access_token": "<crm token>"},
"config": {
"base_url": "https://api.example-crm.com/v2",
"contacts_path": "/people",
"deals_path": "/opportunities",
"activities_path": "/events",
"stage_field": "pipeline_stage",
"value_field": "amount",
"auth_header": "X-API-Key",
"auth_scheme": ""
}
}'

auth_scheme: "" sends the raw token in the header for CRMs that do not use the Bearer prefix. Only the keys above are accepted; unknown config keys are rejected with 422.

Tool Action What it does
get_pipeline_summary read Deal counts by stage, total value, velocity — derived from the deals list
get_deals read List deals with filtering and sorting
get_contacts read List CRM contacts with search and filtering
get_activities read Recent activities (calls, emails, meetings, notes)
create_deal write Create a new deal in the pipeline
update_deal_stage write Move a deal to a different stage

See Permission model. Deal creation and stage updates are routed through the Autonomy Engine and your approval queue according to your autonomy level.

Click the trash icon on the CRM row and confirm; the token is revoked from the vault. Rotate or delete the token in your CRM as well.