Affinity MCP integration for AI agents.
Connect AI agents to Affinity through 20 structured actions, including get company, get current user, and get list. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 20
- 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 Affinity integration exposes
The Affinity Agent App exposes 20 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get one affinity company by id with optional field selectors, get the authenticated affinity user, tenant, and api grant summary, and get one affinity list by id. 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 Affinity account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Affinity capabilities.
Showing 12 of 20 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_companyREADGet one Affinity company by ID with optional field selectors.
INPUTS: companyId / fieldIds / fieldTypes
get_current_userREADGet the authenticated Affinity user, tenant, and API grant summary.
get_listREADGet one Affinity list by ID.
INPUTS: listId
get_opportunityREADGet one Affinity opportunity by ID.
INPUTS: opportunityId
get_personREADGet one Affinity person by ID with optional field selectors.
INPUTS: personId / fieldIds / fieldTypes
get_saved_viewREADGet one Affinity saved view by list ID and saved view ID.
INPUTS: listId / viewId
list_companiesREADList Affinity companies with optional ID and field selectors.
INPUTS: cursor / limit / ids / fieldIds / fieldTypes
list_company_fieldsREADList non-list-specific Affinity company field metadata.
INPUTS: cursor / limit
list_company_list_entriesREADList all Affinity list entries for one company across lists.
INPUTS: companyId / cursor / limit
list_company_listsREADList the Affinity lists that contain one company.
INPUTS: companyId / cursor / limit
list_list_entriesREADList the Affinity list entries for one list with optional field selectors.
INPUTS: listId / cursor / limit / fieldIds / fieldTypes
list_list_fieldsREADList the field metadata for one Affinity list.
INPUTS: listId / cursor / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_company
companyIdREQUIRED- The Affinity company ID.
fieldIdsOPTIONAL- The field IDs for which to return company field data.
fieldTypesOPTIONAL- The field types for which to return company field data.
get_list
listIdREQUIRED- The Affinity list ID.
get_opportunity
opportunityIdREQUIRED- The Affinity opportunity ID.
get_person
personIdREQUIRED- The Affinity person ID.
fieldIdsOPTIONAL- The field IDs for which to return person field data.
fieldTypesOPTIONAL- The field types for which to return person field data.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company
Get one Affinity company by ID with optional field selectors. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_companyVerify with Get Current User
Get the authenticated Affinity user, tenant, and API grant summary. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Affinity with explicit limits
- Authorize Affinity with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Affinity data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Affinity rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Affinity task completed successfully.
CONNECTION MODEL
API key
Affinity API key used with the Authorization Bearer header. Create it in Settings -> Manage Apps -> API Keys.
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
- 20
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- 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 Affinity.