Housecall Pro + Memtro

Only when you ask, and only what it has been granted: create a customer; update a customer; create a job for a customer and address; add a note to a job; add a tag to a job; remove a tag from a job; add a line item to a job; schedule or reschedule a job; remove a job's schedule; dispatch a job to employees; add an appointment to a job; delete an appointment from a job; create a lead; convert a lead to an estimate or a job; create an estimate; approve or decline estimate options. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

API key. In Housecall Pro, open My Apps, All Apps, API Key Management and generate a key. Choose Full access to let Memtro act. Only admins on the MAX plan can do this.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Housecall Pro, choosing the same kinds; the tab shows Housecall Pro's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.