Integration

Verdesk CRM integration

Verdesk is the messaging CRM of Prontuario Verde, the practice-management software for dental, medical and aesthetic clinics. Find, create and tag contacts (patients and leads), manage their phone numbers, e-mail addresses and additional fields, create opportunities and move or close them in funnels, record inbound messages, send messages and template messages on an opportunity's channel (WhatsApp in the vendor samples), and list channels, funnels, stages, resolution types and reasons, templates and users. Contacts are personal data and their additional fields may hold health information. Authentication is OAuth 2.0 client credentials: the client id and secret Prontuario Verde provides for the Verdesk API are exchanged for a Bearer token valid 1 hour; the platform makes that token request itself.

Connect Verdesk CRM How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Verdesk CRM.Built from the 26 Verdesk CRM tools below, on the connection you add once.

What you can do with Verdesk CRM

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Opportunity, 5 operations

close_opportunityClose opportunityPUTAgents: ask firstCloses an opportunity in its funnel with a resolution type (from list_resolution_types) and optional reason, user and notes.
create_opportunityCreate opportunityPOSTAgents: ask firstCreates an opportunity (a lead) for a contact identified by name and phone, with optional e-mail, tags, additional fields, funnel, UTM and Facebook lead data, and returns its id_oportunidade.
list_contact_opportunitiesList contact opportunitiesGETAgents: ask firstLists every opportunity ever created for a contact, open or closed, under items: subject, assignee, date, funnel and stage, situation, resolution type and reason. Contains contact names.
list_funnel_opportunitiesList funnel opportunitiesGETAgents: ask firstLists the active opportunities of a funnel under items: id_oportunidade, subject, contact name, assignee, date, stage and situation. Contains contact names.
move_opportunityMove opportunityPUTAgents: ask firstMoves an opportunity to another stage or funnel: id_funil is required, id_etapa_funil optional. The vendor documents that an opportunity given no destination is put back in the first stage of its original funnel.

Contact, 3 operations

create_contactCreate contactPOSTAgents: ask firstCreates a contact with a name, e-mail addresses and phone numbers and returns its id_contato. Fails when another contact already has one of the same e-mail addresses or phone numbers.
find_contactFind contactGETAgents: ask firstFinds the contacts registered with the given e-mail address or phone number (pass one of the two) and returns them under items: id_contato, name, e-mail addresses, phone numbers and tags. Personal data.
get_contactGet contactGETAgents: ask firstReturns a contact as a one-element list under items: name, e-mail addresses, phone numbers, tags and additional fields (a map of field label to value). Personal data; the additional fields may hold health information.

Contact email, 2 operations

add_contact_emailAdd contact emailPOSTAgents: ask firstAdds an e-mail address to a contact. Fails when the address already belongs to another contact.
delete_contact_emailDelete contact emailDELETEAgents: ask firstDeletes one e-mail address from a contact.

Contact phone, 2 operations

add_contact_phoneAdd contact phonePOSTAgents: ask firstAdds a phone number to a contact. Fails when the number already belongs to another contact.
delete_contact_phoneDelete contact phoneDELETEAgents: ask firstDeletes one phone number from a contact. Fails when the number is not registered on that contact.

Contact tag, 2 operations

add_contact_tagsAdd contact tagsPOSTAgents: ask firstAdds tags to a contact, to classify and segment it. Tags are taken off only all at once, with remove_all_contact_tags.
remove_all_contact_tagsRemove all contact tagsDELETEAgents: ask firstRemoves EVERY tag of a contact at once (no single-tag removal exists). Read the tags first with get_contact and re-add the ones to keep with add_contact_tags.

Inbound message, 2 operations

record_inbound_messageRecord inbound messagePOSTAgents: ask firstRecords in Verdesk a message a contact sent through an outside source, as received on the given channel, and returns the opportunity it is filed in (id_oportunidade). Use send_opportunity_message to reply.
record_inbound_opportunity_messageRecord inbound opportunity messagePOSTAgents: ask firstRecords in Verdesk a message a contact sent through an outside source, as received on the given channel, and links it to an existing opportunity. Use send_opportunity_message to reply.

Template message, 2 operations

list_template_messagesList template messagesGETAgents: ask firstLists the template messages (standard messages) of the account under items: id_mensagem_padrao, name and text. Pass id_mensagem_padrao to send_opportunity_template_message.
send_opportunity_template_messageSend opportunity template messagePOSTAgents: ask firstSENDS a template message (from list_template_messages) to the contact's phone through a channel and records it on the opportunity.

Channel, 1 operation

list_channelsList channelsGETAgents: ask firstLists the messaging channels of the account: id_canal, type (WA in the vendor samples), name and canal, the channel's own number. Pass canal as the channel when sending or recording a message.

Contact field, 1 operation

update_contact_additional_fieldsUpdate contact additional fieldsPUTAgents: ask firstCreates additional fields on a contact or updates the value of existing ones, one entry per field label given.

Funnel, 1 operation

list_funnelsList funnelsGETAgents: ask firstLists the active funnels (pipelines) of the account under items: id_funil and name. Pass id_funil to the funnel tools and when creating or moving an opportunity.

Funnel stage, 1 operation

list_funnel_stagesList funnel stagesGETAgents: ask firstLists the stages of a funnel under items: id_etapa_funil and name. Pass id_etapa_funil to move_opportunity.

Message, 1 operation

send_opportunity_messageSend opportunity messagePOSTAgents: ask firstSENDS a free-text message to the contact's phone through a channel and records it on the opportunity. WhatsApp may refuse free text and answer that a template is required: then use send_opportunity_template_message.

Resolution reason, 1 operation

list_resolution_reasonsList resolution reasonsGETAgents: ask firstLists the resolution reasons available for one resolution type of a funnel under items: id_motivo_resolucao and name. Optional input of close_opportunity.

Resolution type, 1 operation

list_resolution_typesList resolution typesGETAgents: ask firstLists the resolution types of a funnel (for example success or no success) under items: id_tipo_resolucao and name. close_opportunity needs one.

User, 1 operation

list_usersList usersGETAgents: ask firstLists the users (team members) of the account under items: id_usuario, name and e-mail address. Personal data. Pass id_usuario where a tool takes a user.

Use Verdesk CRM from Claude Code, Cursor or Codex

Connect Verdesk CRM in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Verdesk CRM operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Verdesk CRM

Create your workspace
Sign up free. Nothing to install.
Connect Verdesk CRM once
Add your Verdesk CRM connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.