CentralStationCRM MCP integration for AI agents.
Connect AI agents to CentralStationCRM through 19 structured actions, including get company, create company, and delete company. Review authentication, input…
- ACTION CONTRACTS
- 19
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the CentralStationCRM integration exposes
The CentralStationCRM Agent App exposes 19 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent get one centralstationcrm company by identifier, create a company in centralstationcrm, and delete a company from centralstationcrm. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected CentralStationCRM account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real CentralStationCRM capabilities.
Showing 12 of 19 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_companyREADGet one CentralStationCRM company by identifier.
INPUTS: id / includes / methods
create_companyWRITECreate a company in CentralStationCRM.
INPUTS: company / includes / methods / no_log
delete_companyHIGH IMPACTDelete a company from CentralStationCRM.
INPUTS: id / no_log
create_dealWRITECreate a deal in CentralStationCRM.
INPUTS: deal / includes / methods / no_log
create_personWRITECreate a person in CentralStationCRM.
INPUTS: person / includes / methods / no_log
delete_dealHIGH IMPACTDelete a deal from CentralStationCRM.
INPUTS: id / no_log
delete_personHIGH IMPACTDelete a person from CentralStationCRM.
INPUTS: id / no_log
get_dealREADGet one CentralStationCRM deal by identifier.
INPUTS: id / includes / methods
get_personREADGet one CentralStationCRM person by identifier.
INPUTS: id / includes / methods
get_userREADGet the current CentralStationCRM API user.
list_companiesREADList companies in CentralStationCRM with optional paging and tag filters.
INPUTS: page / perpage / order / includes / methods
list_dealsREADList deals in CentralStationCRM with optional paging and tag filters.
INPUTS: page / perpage / order / includes / methods
INPUT CONTRACTS
Know what the action needs before it runs.
get_company
idREQUIRED- The CentralStationCRM numeric record identifier.
includesOPTIONAL- Comma-separated CentralStationCRM includes parameter.
methodsOPTIONAL- Comma-separated CentralStationCRM methods parameter.
create_company
companyREQUIRED- The CentralStationCRM company payload.
includesOPTIONAL- Comma-separated CentralStationCRM includes parameter.
methodsOPTIONAL- Comma-separated CentralStationCRM methods parameter.
no_logOPTIONAL- Whether CentralStationCRM should skip creating a protocol log.
delete_company
idREQUIRED- The CentralStationCRM numeric record identifier.
no_logOPTIONAL- Whether CentralStationCRM should skip creating a protocol log.
create_deal
dealREQUIRED- The CentralStationCRM deal payload.
includesOPTIONAL- Comma-separated CentralStationCRM includes parameter.
methodsOPTIONAL- Comma-separated CentralStationCRM methods parameter.
no_logOPTIONAL- Whether CentralStationCRM should skip creating a protocol log.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company
Get one CentralStationCRM company by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_companyControl Create Company
Create a company in CentralStationCRM. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_companyVerify with Get Deal
Get one CentralStationCRM deal by identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_dealSAFETY BOUNDARY
Operate CentralStationCRM with explicit limits
- Authorize CentralStationCRM with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_company`, `delete_deal`, and `delete_person` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in CentralStationCRM rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the CentralStationCRM task completed successfully.
CONNECTION MODEL
API key
CentralStationCRM API key sent with the X-apikey header. Create or view API keys under Account settings > API: https://centralstationcrm.com/api-basics.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by CentralStationCRM.