AccuLynx
Read and write jobs, contacts, appointments, estimates and invoices in AccuLynx, the roofing contractor CRM and job-management platform.
About
AccuLynx ships in the w6w first-party pack. It declares 29 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.acculynx- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
AccuLynx is the job-management and CRM platform built for roofing and exterior contractors: every customer is a contact, every piece of work is a job that moves through a fixed milestone pipeline (Lead, Prospect, Approved, Completed, Invoiced, Closed), and estimates, invoices, payments, appointments and crew calendars hang off the job.
This app covers AccuLynx’s v2 REST API: list, search, read and create jobs (a new job always starts as an unassigned Lead), correct a job’s address, post to its message feed, and read its representatives, current milestone, estimates and invoices. It manages contacts (list, search, create, update, add notes, list a contact’s jobs), reads company calendars and their appointments, and exposes the lookups other calls need: users, lead sources, countries and states, and company settings.
Authentication is a single API key sent as a bearer token. AccuLynx issues API keys to its own customers only; there is no sandbox. Health checks track AccuLynx’s status page (its dedicated API component) and its unauthenticated ping endpoint.
Build with AccuLynx
Three routes to the same 29 actions. The Workflow tab is generated from AccuLynx's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Calendar Appointments
appointment-list List a calendar's appointments within a date range, optionally for one job or one event type.
Create Contact
contact-create Create a contact. Phone numbers and email addresses are arrays exactly as AccuLynx documents them.
List Contacts
contact-list List contacts. Phone numbers and email addresses come back as links unless expanded with includes.
Search Contacts
contact-search Search contacts by term and contact type within a created-date window.
List Contact Types
contact-type-list List the company's contact types; ids feed Create Contact and Update Contact.
Update Contact
contact-update Update a contact. AccuLynx requires lastName and contactTypeIds on every update, so send them even if unchanged. Phone numbers, emails and notes are not changed by this endpoint.
Create Job
job-create Create a job for an existing contact. AccuLynx creates it in the Lead milestone, unassigned. The location address is optional but, if any part is given, street, city, state, country and ZIP are all required.
List Job Estimates
job-estimates-list List a job's estimates (ids and links; use Get Estimate for the totals).
List Jobs
job-list List jobs, optionally filtered by milestone and a created/milestone/modified date range. Unassigned leads are excluded unless assignment=unassigned.
Post Job Message
job-message-create Post a comment to a job's message feed, visible in the job's Messages section in AccuLynx.
Get Current Job Milestone
job-milestone-current Get the milestone a job is in now (Lead, Prospect, Approved, Completed, Invoiced, Closed or Cancelled) with its statuses.
List Job Representatives
job-representatives-list List the users assigned to a job: company representative, sales owner, A/R owner and additional representatives.
Search Jobs
job-search Find jobs by a search term, by proximity to a map point, or both (both must match). At least one of search term or latitude/longitude is required.
Update Job Address
job-update-address Update a job's location address. Only the fields you send are changed.
List Lead Sources
lead-source-list List the company's active lead sources (with child sources); ids feed Create Job.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying AccuLynx's real ids.
{
"manifestVersion": "2",
"name": "acculynx-example",
"steps": [
{
"id": "appointment-get",
"uses": {
"app": "io.w6w.acculynx",
"action": "appointment-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"calendarId": "<calendarId>",
"appointmentId": "<appointmentId>"
}
}
]
}Here are some of the things you can do
-
Get Appointment
readappointment-get -
List Calendar Appointments
readappointment-list -
List Calendars
readcalendar-list -
Get Company Settings
readcompany-settings-get -
Create Contact
performcontact-create
+24 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for AccuLynx, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to AccuLynx. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "appointment-get",
payload: {
calendarId: "<value>",
appointmentId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action appointment-get --payload '{"calendarId":"<value>","appointmentId":"<value>"}'Give an AI agent AccuLynx — without giving it AccuLynx's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.acculynx#appointment-get",
"input": {
"calendarId": "<calendarId>",
"appointmentId": "<appointmentId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's AccuLynx connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
AccuLynx's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. AccuLynx itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
AccuLynx declares its own checks, so its health is a property of the app rather than something the host guesses at.
AccuLynx platform status
The "API" component from status.acculynx.com, plus the rest of AccuLynx's own status page for visibility.
AccuLynx API reachability
Unsigned GET /diagnostics/ping. 200 with a `date` field (or a schema-correct 401) proves the API is answering. Says nothing about any credential.