Nectar CRM integration
Nectar CRM is a Brazilian sales CRM. With this API an agent can list, look up (by id, email, phone, CNPJ or CPF), create, update and upsert contacts; manage sales opportunities and lead qualifications with their pipeline statistics and next activities; manage appointments, tasks, feedback posts and their comments; read forms; manage products, price tables, proposals and pipelines; and list or create users, teams, segments, origins, tags, contact and product categories, call and appointment types, distribution queues, custom fields and webhooks. The vendor documents its Remove routes without an id or body, so no delete is exposed except for queues. Field names are Portuguese, as the API expects them. Listings are paged (page; -1 returns up to 200). Authentication is the public token from Settings, Integrations, sent in the Access-Token header.
Say what should happen.
The workflow builds itself.
What you can do with Nectar 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.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Compromisso, 4 operations
create_appointmentCreate appointmentPOSTCreates an appointment. assunto, dataInicio, dataFim and cliente are required. Returns the appointment.get_appointmentGet appointmentGETGets one appointment by ID: subject, client, start and end, location, participants, status and responsible user.list_appointmentsList appointmentsGETLists appointments, paged, filtered by dates, subject, client, opportunity, author, type, responsible user or users.update_appointmentUpdate appointmentPUTUpdates an appointment by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Contato, 4 operations
create_contactCreate contactPOSTCreates a contact. nome and constante (section) are required. Origin, category and segment given by name are created when they do not exist. Returns the contact.get_contactGet contactGETGets one contact by ID: names, documents (CNPJ, CPF), emails, phones, addresses, tags, origin, segment, responsible user and custom fields.list_contactsList contactsGETLists contacts (clients, prospects, suspects, leads), paged, filtered by name or code, section (constante), dates, tags, origin, segment, responsible users or custom fields.update_contactUpdate contactPUTUpdates a contact by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Oportunidade, 4 operations
create_opportunityCreate opportunityPOSTCreates a sales opportunity for a contact (cliente.id) in a pipeline stage. nome and cliente are required. Returns the opportunity.get_opportunityGet opportunityGETGets one opportunity by ID: client, pipeline and stage, status, probability, values, products and custom fields.list_opportunitiesList opportunitiesGETLists sales opportunities, paged. Without status only in-progress ones are returned. Filter by dates, name, code, section, categories, products, tags, origins, segments, users or custom fields.update_opportunityUpdate opportunityPUTUpdates an opportunity by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Produto, 4 operations
create_productCreate productPOSTCreates a product. nome and valorBase are required. The vendor shows no response body for this route.get_productGet productGETGets one product by ID: code, price, currency, recurrence, category, discount and commission settings, stock.list_productsList productsGETLists products, paged, filtered by name, code, category, subcategory, recurrence or stock.update_productUpdate productPUTUpdates a product by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Qualificacoe, 4 operations
create_qualificationCreate qualificationPOSTCreates a lead qualification for a contact in a qualification pipeline. The vendor shows no response body for this route.get_qualificationGet qualificationGETGets one qualification by ID: client, pipeline and stage, status, due date and responsible user.list_qualificationsList qualificationsGETLists lead qualifications, paged, filtered by status, dates, client, name or code, section or users.update_qualificationUpdate qualificationPUTUpdates a qualification by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Queue, 4 operations
create_queuesCreate queuesPOSTCreates queue from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create. Only admins may change queues.delete_queueDelete queueDELETEDeletes a queue by ID. Only admins may change queues; it cannot be undone.get_queueGet queueGETGets one queue by ID with its users and strategy.list_queuesList queuesGETLists distribution queues (rotating responsible users for new contacts and opportunities), filtered by name prefix.
Tabela preco, 4 operations
create_price_tableCreate price tablePOSTCreates a price table. nome is required. The vendor shows no response body for this route.get_price_tableGet price tableGETGets one price table by ID with its products.list_price_tablesList price tablesGETLists price tables, paged, filtered by name or active, with their products.update_price_tableUpdate price tablePUTUpdates a price table by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Tarefa, 4 operations
create_taskCreate taskPOSTCreates a task. titulo, dataLimite and cliente are required. Returns the task.get_taskGet taskGETGets one task by ID: title, client, due date, priority, status, type and, for call tasks, the call result.list_tasksList tasksGETLists tasks, paged, filtered by title, client, opportunity, author, type, dates or users.update_taskUpdate taskPUTUpdates a task by ID. The vendor describes PUT as replacing the stored data with the request (for contacts it says an omitted field keeps its value and null, "", {} or [] clears it): read the record first and send back the fields to keep.
Tipo, 4 operations
create_appointment_typesCreate appointment typesPOSTCreates appointment type from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.create_call_typesCreate call typesPOSTCreates call type from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_appointment_typesList appointment typesGETLists appointment types.list_call_typesList call typesGETLists call types (used on call tasks).
Email, 3 operations
find_contacts_by_emailFind contacts by emailGETFinds contacts by email (* works as a wildcard). Returns the matching record(s) with the same fields as list_contacts; the vendor shows no response sample for this route.find_opportunities_by_emailFind opportunities by emailGETFinds opportunities by their contact's email (* works as a wildcard). Returns the matching record(s) with the same fields as list_opportunities; the vendor shows no response sample for this route.find_qualifications_by_emailFind qualifications by emailGETFinds qualifications by their contact's email. Returns the matching record(s) with the same fields as list_qualifications; the vendor shows no response sample for this route.
Formulario, 3 operations
create_formsCreate formsPOSTCreates form from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.get_formGet formGETGets one form by ID with its answers.list_formsList formsGETLists filled forms, paged, with template, answers and dates.
Publicacao, 3 operations
create_feedbackCreate feedbackPOSTCreates a feedback post (note) linked to a contact, opportunity or task. The vendor shows no response body for this route.get_feedbackGet feedbackGETGets one feedback post by ID.list_feedbacksList feedbacksGETLists feedback posts (notes), paged, with subject, text, author, linked contact, opportunity or task, and comment count.
Telefone, 3 operations
find_contacts_by_phoneFind contacts by phoneGETFinds contacts by phone (* works as a wildcard). Returns the matching record(s) with the same fields as list_contacts; the vendor shows no response sample for this route.find_opportunities_by_phoneFind opportunities by phoneGETFinds opportunities by their contact's phone (* works as a wildcard). Returns the matching record(s) with the same fields as list_opportunities; the vendor shows no response sample for this route.find_qualifications_by_phoneFind qualifications by phoneGETFinds qualifications by their contact's phone. Returns the matching record(s) with the same fields as list_qualifications; the vendor shows no response sample for this route.
Categoria, 2 operations
create_contact_categoriesCreate contact categoriesPOSTCreates contact category from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_contact_categoriesList contact categoriesGETLists contact categories with the contact sections they appear in, filtered by name.
Contato id, 2 operations
find_opportunities_by_contactFind opportunities by contactGETFinds the opportunities of one contact by contact ID. Returns the matching record(s) with the same fields as list_opportunities; the vendor shows no response sample for this route.find_qualifications_by_contactFind qualifications by contactGETFinds the qualifications of one contact by contact ID. Returns the matching record(s) with the same fields as list_qualifications; the vendor shows no response sample for this route.
Equipe, 2 operations
create_teamsCreate teamsPOSTCreates team from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_teamsList teamsGETLists the user teams.
Lista, 2 operations
create_tagsCreate tagsPOSTCreates tag from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_tagsList tagsGETLists tags, optionally only those related to contacts or opportunities, or that the user can see.
Origem, 2 operations
create_originsCreate originsPOSTCreates origin from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_originsList originsGETLists contact and opportunity origins.
Pipeline, 2 operations
create_pipelinesCreate pipelinesPOSTCreates pipeline from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_pipelinesList pipelinesGETLists sales or qualification pipelines with their stages and rules. type 0 = sales, 1 = qualification.
Produto categoria, 2 operations
create_product_categoriesCreate product categoriesPOSTCreates product category from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_product_categoriesList product categoriesGETLists product categories with their subcategories.
Produto sub categoria, 2 operations
create_product_subcategoriesCreate product subcategoriesPOSTCreates product subcategory from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_product_subcategoriesList product subcategoriesGETLists product subcategories with their category.
Proxima atividade, 2 operations
get_contact_next_activityGet contact next activityGETGets the next activity (task or appointment) of one contact as Nectar returns it (the vendor documents no response fields).get_opportunity_next_activityGet opportunity next activityGETGets the next activity of one opportunity as Nectar returns it (the vendor documents no response fields).
Segmento, 2 operations
create_segmentsCreate segmentsPOSTCreates segment from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_segmentsList segmentsGETLists contact segments, filtered by name.
Statistic, 2 operations
get_contact_statisticsGet contact statisticsGETGets the statistics of one contact as Nectar returns them (the vendor documents no response fields).get_opportunity_statisticsGet opportunity statisticsGETGets the statistics of one opportunity as Nectar returns them (the vendor documents no response fields).
Usuario, 2 operations
create_usersCreate usersPOSTCreates user from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.list_usersList usersGETLists the Nectar users with login, email and active flag.
Campo personalizado, 1 operation
list_custom_fieldsList custom fieldsGETLists the custom fields of contacts, products, opportunities and Leadboard with alias, type, options and section.
Cnpj, 1 operation
find_contacts_by_cnpjFind contacts by cnpjGETFinds contacts by CNPJ. Returns the matching record(s) with the same fields as list_contacts; the vendor shows no response sample for this route.
Comentario, 1 operation
add_feedback_commentAdd feedback commentPOSTAdds a comment to a feedback post. The vendor shows no response body for this route.
Cpf, 1 operation
find_contacts_by_cpfFind contacts by cpfGETFinds contacts by CPF. Returns the matching record(s) with the same fields as list_contacts; the vendor shows no response sample for this route.
Incluir com anexo, 1 operation
create_feedback_with_attachmentCreate feedback with attachmentPOSTCreates a feedback post with a file attached (multipart): publicacao is the post as a JSON string, anexos the file.
Opportunity, 1 operation
list_opportunity_proposalsList opportunity proposalsGETLists the proposals of one opportunity, with status, version, code and public download URL.
Pipe, 1 operation
get_pipeline_stage_statisticsGet pipeline stage statisticsGETGets opportunity statistics per stage of one sales pipeline, as Nectar returns them (the vendor documents no response fields).
Proposta, 1 operation
create_proposalsCreate proposalsPOSTCreates proposal from a JSON array (the vendor documents this create with an array sample). The vendor shows no response body for this create.
Total, 1 operation
get_pipeline_total_statisticsGet pipeline total statisticsGETGets the total opportunity statistics of one sales pipeline, as Nectar returns them (the vendor documents no response fields).
Upsert, 1 operation
upsert_contactUpsert contactPOSTCreates a contact, or updates the one matched by mail, phone, cnpj or cpf (in that priority). The vendor shows no response body for this route.
Webhook, 1 operation
list_webhooksList webhooksGETLists webhooks with name, URL, event number, active flag and success counter.
Use Nectar CRM from Claude Code, Cursor or Codex
Connect Nectar CRM in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Nectar CRM operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Nectar CRM
- Create your workspace
Sign up free. Nothing to install.
- Connect Nectar CRM once
Add your Nectar 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.
Nectar CRM integration FAQ
What can you do with the Nectar CRM integration?
LiveContext exposes 83 operations on Nectar CRM, covering compromisso, contato, oportunidade and produto.
