AccuLynx MCP integration for AI agents.
Connect AI agents to AccuLynx through 12 structured actions, including get company settings, create contact, and create job. Review authentication, inputs, w…
- ACTION CONTRACTS
- 12
- 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 AccuLynx integration exposes
The AccuLynx Agent App exposes 12 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent get the current acculynx company settings for the connected location, create one new contact in acculynx, and create one new job in the acculynx lead milestone. 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 AccuLynx account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AccuLynx capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_company_settingsREADGet the current AccuLynx company settings for the connected location.
create_contactWRITECreate one new contact in AccuLynx.
INPUTS: contactTypeIds / firstName / lastName / crossReference / companyName
create_jobWRITECreate one new job in the AccuLynx Lead milestone.
INPUTS: contact / leadSource / locationAddress / priority / jobCategory
get_initial_appointmentREADGet the initial appointment for one AccuLynx job.
INPUTS: jobId
list_calendar_appointmentsREADList appointment summaries for one AccuLynx calendar within a date range.
INPUTS: calendarId / pageSize / pageStartIndex / startDate / endDate
list_calendarsREADList the calendars available in the current AccuLynx location.
INPUTS: pageSize / recordStartIndex
list_contact_typesREADList the contact types configured for the current AccuLynx company.
INPUTS: pageSize / pageStartIndex
list_job_categoriesREADList the active AccuLynx job categories configured for the company.
INPUTS: pageSize / recordStartIndex
list_lead_sourcesREADList the active lead sources configured for the current AccuLynx company.
INPUTS: pageSize / recordStartIndex
list_trade_typesREADList the active AccuLynx trade types configured for the company.
INPUTS: pageSize / recordStartIndex
list_work_typesREADList the active AccuLynx work types configured for the company.
INPUTS: pageSize / recordStartIndex
upsert_initial_appointmentWRITEAdd or update the initial appointment for one AccuLynx job.
INPUTS: jobId / startDate / endDate / notes
INPUT CONTRACTS
Know what the action needs before it runs.
create_contact
contactTypeIdsREQUIRED- The contact type identifiers assigned to the contact.
firstNameOPTIONAL- The contact first name.
lastNameOPTIONAL- The contact last name.
crossReferenceOPTIONAL- The external cross-reference stored on the contact.
companyNameOPTIONAL- The contact company name.
create_job
contactREQUIRED- The contact reference used by a job.
leadSourceOPTIONAL- The lead source reference used by a job.
locationAddressOPTIONAL- The job location address.
priorityOPTIONAL- The priority assigned to the job.
jobCategoryOPTIONAL- The job category reference.
get_initial_appointment
jobIdREQUIRED- The unique identifier of the job.
list_calendar_appointments
calendarIdREQUIRED- The unique identifier of the calendar.
pageSizeOPTIONAL- The number of items to return per page.
pageStartIndexOPTIONAL- The zero-based index of the first item to return.
startDateREQUIRED- The inclusive start date in YYYY-MM-DD format.
endDateREQUIRED- The inclusive end date in YYYY-MM-DD format.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company Settings
Get the current AccuLynx company settings for the connected location. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_company_settingsControl Create Contact
Create one new contact in AccuLynx. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Initial Appointment
Get the initial appointment for one AccuLynx job. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_initial_appointmentSAFETY BOUNDARY
Operate AccuLynx with explicit limits
- Authorize AccuLynx with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 AccuLynx rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AccuLynx task completed successfully.
CONNECTION MODEL
API key
AccuLynx API key used with the Authorization Bearer header. Create or view your key on the official AccuLynx API Keys page: https://my.acculynx.com/apikeys
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
- 9
- WRITE SIGNALS
- 3
- 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 AccuLynx.