Integration

Ploomes integration

Ploomes is a Brazilian sales CRM. Query, create, update and delete customers (people and companies), deals (win, lose, reopen), interaction records, tasks, quotes, sales orders, documents, products and their families, groups and parts, tags, teams, custom fields and option tables, pipelines, webhooks and the reference lists behind their ids. Lists take OData query options ($filter, $orderby, $select, $top, $skip); Contacts, Deals, Tasks, Orders, Quotes and Cities return at most 300 records per call. $expand is offered only on cities, countries, states, tags and option tables, because related records can hold users' API keys, so custom field values (OtherProperties) can be written but not read back. Customers, deals, tasks and users hold personal data. Not exposed: creating, changing or deleting users (it takes a password). The API serves up to 120 requests per minute for the whole account. Authentication is the User-Key of an integration user (Administration > Integration users in Ploomes, admins only), sent in the User-Key header.

Connect Ploomes How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ploomes.Built from the 126 Ploomes tools below, on the connection you add once.

What you can do with Ploomes

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.

Contact, 2 operations

create_contactCreate contactPOSTAgents: ask firstCreates a customer, a person or a company (TypeId from list_contact_types), with phones, address, tags and custom fields (OtherProperties). Returns it. Personal data.
list_contactsList contactsGETAgents: ask firstLists customers (people and companies). OData query: $filter, $orderby, $select, $top and $skip for paging. At most 300 per call. Personal data: names, emails, phones, addresses, CPF or CNPJ.

Contacts id, 2 operations

delete_contactDelete contactDELETEAgents: ask firstDeletes a customer (person or company) permanently.
update_contactUpdate contactPATCHAgents: ask firstUpdates a customer (person or company): send only the fields to change (a partial update). Returns the record. Personal data: names, emails, phones, addresses, CPF or CNPJ.

Contacts lines of business, 2 operations

create_contact_line_of_businessCreate contact line of businessPOSTAgents: ask firstCreates a customer line of business and returns it.
list_contact_lines_of_businessList contact lines of businessGETAgents: ask firstLists customer lines of business. OData query: $filter, $orderby, $select, $top and $skip for paging.

Contacts lines of business id, 2 operations

delete_contact_line_of_businessDelete contact line of businessDELETEAgents: ask firstDeletes a customer line of business permanently.
update_contact_line_of_businessUpdate contact line of businessPATCHAgents: ask firstUpdates a customer line of business: send only the fields to change (a partial update). Returns the record.

Contacts numbers of employee, 2 operations

create_contact_employee_rangeCreate contact employee rangePOSTAgents: ask firstCreates a employee-count range for customers and returns it.
list_contact_employee_rangesList contact employee rangesGETAgents: ask firstLists employee-count ranges for customers. OData query: $filter, $orderby, $select, $top and $skip for paging.

Contacts numbers of employees id, 2 operations

delete_contact_employee_rangeDelete contact employee rangeDELETEAgents: ask firstDeletes a employee-count range for customers permanently.
update_contact_employee_rangeUpdate contact employee rangePATCHAgents: ask firstUpdates a employee-count range for customers: send only the fields to change (a partial update). Returns the record.

Contacts origin, 2 operations

create_contact_originCreate contact originPOSTAgents: ask firstCreates a customer origin and returns it.
list_contact_originsList contact originsGETAgents: ask firstLists customer origins. OData query: $filter, $orderby, $select, $top and $skip for paging.

Contacts origins id, 2 operations

delete_contact_originDelete contact originDELETEAgents: ask firstDeletes a customer origin permanently.
update_contact_originUpdate contact originPATCHAgents: ask firstUpdates a customer origin: send only the fields to change (a partial update). Returns the record.

Contacts product, 2 operations

create_contact_productCreate contact productPOSTAgents: ask firstCreates a product linked to a customer and returns it.
list_contact_productsList contact productsGETAgents: ask firstLists products linked to customers. OData query: $filter, $orderby, $select, $top and $skip for paging.

Contacts products id, 2 operations

delete_contact_productDelete contact productDELETEAgents: ask firstDeletes a product linked to a customer permanently.
update_contact_productUpdate contact productPATCHAgents: ask firstUpdates a product linked to a customer: send only the fields to change (a partial update). Returns the record.

Deal, 2 operations

create_dealCreate dealPOSTAgents: ask firstCreates a deal with a title, a customer (ContactId; left out, the account's placeholder customer), a stage (StageId from list_deal_stages; left out, the first stage of an open pipeline) and an amount. Returns the deal.
list_dealsList dealsGETAgents: ask firstLists deals (sales opportunities). OData query: $filter, $orderby, $select, $top and $skip for paging. At most 300 per call. Includes customer and owner references.

Deals id, 2 operations

delete_dealDelete dealDELETEAgents: ask firstDeletes a deal permanently.
update_dealUpdate dealPATCHAgents: ask firstUpdates a deal: send only the fields to change (a partial update). Returns the record. Includes customer and owner references.

Deals pipeline, 2 operations

create_deal_pipelineCreate deal pipelinePOSTAgents: ask firstCreates a deal pipeline and returns it.
list_deal_pipelinesList deal pipelinesGETAgents: ask firstLists deal pipelines (funnels). OData query: $filter, $orderby, $select, $top and $skip for paging.

Deals pipelines id, 2 operations

delete_deal_pipelineDelete deal pipelineDELETEAgents: ask firstDeletes a deal pipeline permanently.
update_deal_pipelineUpdate deal pipelinePATCHAgents: ask firstUpdates a deal pipeline: send only the fields to change (a partial update). Returns the record.

Department, 2 operations

create_departmentCreate departmentPOSTAgents: ask firstCreates a department and returns it.
list_departmentsList departmentsGETAgents: ask firstLists departments of customers' contacts. OData query: $filter, $orderby, $select, $top and $skip for paging.

Departments id, 2 operations

delete_departmentDelete departmentDELETEAgents: ask firstDeletes a department permanently.
update_departmentUpdate departmentPATCHAgents: ask firstUpdates a department: send only the fields to change (a partial update). Returns the record.

Document, 2 operations

create_documentCreate documentPOSTAgents: ask firstCreates a document and returns it.
list_documentsList documentsGETAgents: ask firstLists documents generated from templates. OData query: $filter, $orderby, $select, $top and $skip for paging.

Documents id, 2 operations

delete_documentDelete documentDELETEAgents: ask firstDeletes a document permanently.
update_documentUpdate documentPATCHAgents: ask firstUpdates a document: send only the fields to change (a partial update). Returns the record.

Field, 2 operations

create_fieldCreate fieldPOSTAgents: ask firstCreates a custom field and returns it. A request formula's headers and body are set in Ploomes, not here; its URL, headers and body are withheld from the answer.
list_fieldsList fieldsGETAgents: ask firstLists custom fields. OData query: $filter, $orderby, $top and $skip for paging. A request formula's URL, headers and body are withheld: they can carry a third-party API's credentials.

Fields key, 2 operations

delete_fieldDelete fieldDELETEAgents: ask firstDeletes a custom field permanently, with the values every record holds for it.
update_fieldUpdate fieldPATCHAgents: ask firstUpdates a custom field (by its Key): send only the fields to change. Returns the field. A request formula's headers and body are set in Ploomes, not here; its URL, headers and body are withheld from the answer.

Fields options table, 2 operations

create_field_option_tableCreate field option tablePOSTAgents: ask firstCreates a option table of custom fields and returns it.
list_field_option_tablesList field option tablesGETAgents: ask firstLists option tables of custom fields. OData query: $filter, $orderby, $select and $expand (related records), $top and $skip for paging.

Fields options tables option, 2 operations

create_field_optionCreate field optionPOSTAgents: ask firstCreates a option of a custom-field option table and returns it.
list_field_optionsList field optionsGETAgents: ask firstLists options of custom-field option tables. OData query: $filter, $orderby, $select and $expand (related records), $top and $skip for paging.

Fields options tables options id, 2 operations

delete_field_optionDelete field optionDELETEAgents: ask firstDeletes a option of a custom-field option table permanently.
update_field_optionUpdate field optionPATCHAgents: ask firstUpdates a option of a custom-field option table: send only the fields to change (a partial update). Returns the record.

Interaction record, 2 operations

create_interaction_recordCreate interaction recordPOSTAgents: ask firstCreates a interaction record (a logged call, email, meeting or note) and returns it. Personal data.
list_interaction_recordsList interaction recordsGETAgents: ask firstLists interaction records (logged calls, emails, meetings, notes). OData query: $filter, $orderby, $select, $top and $skip for paging. Personal data.

Interaction records id, 2 operations

delete_interaction_recordDelete interaction recordDELETEAgents: ask firstDeletes a interaction record (a logged call, email, meeting or note) permanently.
update_interaction_recordUpdate interaction recordPATCHAgents: ask firstUpdates a interaction record (a logged call, email, meeting or note): send only the fields to change (a partial update). Returns the record. Personal data.

Order, 2 operations

create_orderCreate orderPOSTAgents: ask firstCreates a sales order and returns it. Personal data.
list_ordersList ordersGETAgents: ask firstLists sales orders. OData query: $filter, $orderby, $select, $top and $skip for paging. At most 300 per call. Personal data.

Orders id, 2 operations

delete_orderDelete orderDELETEAgents: ask firstDeletes a sales order permanently.
update_orderUpdate orderPATCHAgents: ask firstUpdates a sales order: send only the fields to change (a partial update). Returns the record. Personal data.

Orders stage, 2 operations

create_order_stageCreate order stagePOSTAgents: ask firstCreates a order stage and returns it.
list_order_stagesList order stagesGETAgents: ask firstLists order stages. OData query: $filter, $orderby, $select, $top and $skip for paging.

Orders stages id, 2 operations

delete_order_stageDelete order stageDELETEAgents: ask firstDeletes a order stage permanently.
update_order_stageUpdate order stagePATCHAgents: ask firstUpdates a order stage: send only the fields to change (a partial update). Returns the record.

Product, 2 operations

create_productCreate productPOSTAgents: ask firstCreates a product and returns it.
list_productsList productsGETAgents: ask firstLists products. OData query: $filter, $orderby, $select, $top and $skip for paging.

Products families id, 2 operations

delete_product_familyDelete product familyDELETEAgents: ask firstDeletes a product family permanently.
update_product_familyUpdate product familyPATCHAgents: ask firstUpdates a product family: send only the fields to change (a partial update). Returns the record.

Products family, 2 operations

create_product_familyCreate product familyPOSTAgents: ask firstCreates a product family and returns it.
list_product_familiesList product familiesGETAgents: ask firstLists product families. OData query: $filter, $orderby, $select, $top and $skip for paging.

Products group, 2 operations

create_product_groupCreate product groupPOSTAgents: ask firstCreates a product group and returns it.
list_product_groupsList product groupsGETAgents: ask firstLists product groups. OData query: $filter, $orderby, $select, $top and $skip for paging.

Products groups id, 2 operations

delete_product_groupDelete product groupDELETEAgents: ask firstDeletes a product group permanently.
update_product_groupUpdate product groupPATCHAgents: ask firstUpdates a product group: send only the fields to change (a partial update). Returns the record.

Products id, 2 operations

delete_productDelete productDELETEAgents: ask firstDeletes a product permanently.
update_productUpdate productPATCHAgents: ask firstUpdates a product: send only the fields to change (a partial update). Returns the record.

Products part, 2 operations

create_product_partCreate product partPOSTAgents: ask firstCreates a product part (a component of a configurable product) and returns it.
list_product_partsList product partsGETAgents: ask firstLists product parts. OData query: $filter, $orderby, $select, $top and $skip for paging.

Products parts id, 2 operations

delete_product_partDelete product partDELETEAgents: ask firstDeletes a product part (a component of a configurable product) permanently.
update_product_partUpdate product partPATCHAgents: ask firstUpdates a product part (a component of a configurable product): send only the fields to change (a partial update). Returns the record.

Quote, 2 operations

create_quoteCreate quotePOSTAgents: ask firstCreates a quote and returns it. Personal data.
list_quotesList quotesGETAgents: ask firstLists quotes (proposals). OData query: $filter, $orderby, $select, $top and $skip for paging. At most 300 per call. Personal data.

Role, 2 operations

create_roleCreate rolePOSTAgents: ask firstCreates a contact role (job title) and returns it.
list_rolesList rolesGETAgents: ask firstLists contact roles (job titles). OData query: $filter, $orderby, $select, $top and $skip for paging.

Tag, 2 operations

create_tagCreate tagPOSTAgents: ask firstCreates a tag and returns it.
list_tagsList tagsGETAgents: ask firstLists tags. OData query: $filter, $orderby, $select and $expand (related records), $top and $skip for paging.

Task, 2 operations

create_taskCreate taskPOSTAgents: ask firstCreates a task and returns it. Personal data.
list_tasksList tasksGETAgents: ask firstLists tasks. OData query: $filter, $orderby, $select, $top and $skip for paging. At most 300 per call. Personal data.

Team, 2 operations

create_teamCreate teamPOSTAgents: ask firstCreates a team of users and returns it.
list_teamsList teamsGETAgents: ask firstLists teams of users. OData query: $filter, $orderby, $select, $top and $skip for paging.

Webhook, 2 operations

create_webhookCreate webhookPOSTAgents: ask firstRegisters a webhook: Ploomes POSTs to CallbackUrl when the chosen action (ActionId) happens on an entity (EntityId). Answer 200 quickly: a failed delivery is retried up to 10 times, with growing intervals.
list_webhooksList webhooksGETAgents: ask firstLists the account's webhooks: entity, action, name and callback url. OData query: $filter, $top, $skip.

Account, 1 operation

get_accountGet accountGETAgents: ask firstReturns the company account behind the User-Key: Id, name, email, phone, website, CNPJ, address and city.

Account id, 1 operation

update_accountUpdate accountPATCHAgents: ask firstUpdates the company account behind the User-Key (name, email, phone, website, CNPJ, address). Id is required by the route but any number works: the key decides the account.

Cities countries state, 1 operation

list_statesList statesGETAgents: ask firstLists states (Id, abbreviation, name, country) to fill StateId, with OData $filter, $orderby, $select, $top and $skip.

Cities country, 1 operation

list_countriesList countriesGETAgents: ask firstLists countries (Id, name, short code) to fill CountryId, with OData $filter, $orderby, $select, $top and $skip.

City, 1 operation

list_citiesList citiesGETAgents: ask firstLists cities (Id, name, state, country, IBGE code) to fill CityId. OData query options: $filter (for example by Name), $orderby, $select, $top and $skip; at most 300 per call.

Contacts relationship, 1 operation

list_contact_relationshipsList contact relationshipsGETAgents: ask firstLists the customer relationship types (Id and name) used in RelationshipId.

Contacts status, 1 operation

list_contact_statusesList contact statusesGETAgents: ask firstLists the customer statuses (Id and name) used in StatusId.

Contacts type, 1 operation

list_contact_typesList contact typesGETAgents: ask firstLists the customer types (company or person, Id and name) used in TypeId.

Currency, 1 operation

list_currenciesList currenciesGETAgents: ask firstLists the currencies (Id, name, symbol) used in CurrencyId.

Deals loss reason, 1 operation

list_deal_loss_reasonsList deal loss reasonsGETAgents: ask firstLists the reasons a deal can be lost (Id, name, pipeline), used by lose_deal. OData query options: $filter, $orderby, $select, $top, $skip.

Deals stage, 1 operation

list_deal_stagesList deal stagesGETAgents: ask firstLists the stages of the deal pipelines (Id, name, pipeline, order), used in StageId. OData query options: $filter, $orderby, $select, $top, $skip.

Deals status, 1 operation

list_deal_statusesList deal statusesGETAgents: ask firstLists the deal statuses (open, won, lost: Id and name) used in StatusId.

Document template, 1 operation

list_document_templatesList document templatesGETAgents: ask firstLists the document templates (Id, name, entity) used in TemplateId of documents, quotes and orders, with OData $filter, $orderby, $select, $top and $skip.

Fields entity, 1 operation

list_field_entitiesList field entitiesGETAgents: ask firstLists the Ploomes entities (customers, deals, orders, ...) with Id, names and API url, used in EntityId of custom fields, tags and webhooks.

Fields type, 1 operation

list_field_typesList field typesGETAgents: ask firstLists the custom field types (Id and name: text, number, date, option list, ...) used in TypeId of create_field.

Finish, 1 operation

finish_taskFinish taskPOSTAgents: ask firstMarks a task as finished. Returns the task.

Lose, 1 operation

lose_dealLose dealPOSTAgents: ask firstMarks a deal as lost with a loss reason (LossReasonId from list_deal_loss_reasons). The pipeline's rules apply. Returns the deal.

Operation, 1 operation

list_operationsList operationsGETAgents: ask firstLists the OData operations Ploomes supports (Id, name and the identifier used in $filter expressions).

Phone type, 1 operation

list_phone_typesList phone typesGETAgents: ask firstLists the phone types (Id and name) used in a phone's TypeId.

Quotes approval status, 1 operation

list_quote_approval_statusesList quote approval statusesGETAgents: ask firstLists the quote approval statuses (Id and name).

Quotes id, 1 operation

delete_quoteDelete quoteDELETEAgents: ask firstDeletes a quote permanently.

Relative date, 1 operation

list_relative_datesList relative datesGETAgents: ask firstLists the relative dates Ploomes understands in filters (today, this week, ...), with Id, name and identifier.

Reopen, 1 operation

reopen_dealReopen dealPOSTAgents: ask firstReopens a won or lost deal. The pipeline's rules apply. Returns the deal.

Review, 1 operation

create_quote_reviewCreate quote reviewPOSTAgents: ask firstCreates a new revision of a quote, with its sections, currency and amount. Returns the quote.

Tags id, 1 operation

delete_tagDelete tagDELETEAgents: ask firstDeletes a tag permanently.

Tasks email reminder, 1 operation

list_task_email_remindersList task email remindersGETAgents: ask firstLists the email reminder options of tasks (Id and name).

Tasks id, 1 operation

delete_taskDelete taskDELETEAgents: ask firstDeletes a task permanently.

Tasks repeat interval unit, 1 operation

list_task_repeat_interval_unitsList task repeat interval unitsGETAgents: ask firstLists the repeat interval units of recurring tasks (Id and name) used in RepeatIntervalUnitId.

Tasks type, 1 operation

list_task_typesList task typesGETAgents: ask firstLists the task types (Id and name) used in TypeId of tasks.

Teams id, 1 operation

delete_teamDelete teamDELETEAgents: ask firstDeletes a team of users permanently.

User, 1 operation

list_usersList usersGETAgents: ask firstLists the users of the account (name, email, phone, role, profile, social links, suspension). OData query: $filter, $top, $skip. Personal data.

Users profile, 1 operation

list_user_profilesList user profilesGETAgents: ask firstLists the user permission profiles (Id and name) used in ProfileId of users, with OData $filter, $select, $top and $skip.

Webhooks action, 1 operation

list_webhook_actionsList webhook actionsGETAgents: ask firstLists the webhook actions (create, update, delete, win, lose, ...: Id and name) used in ActionId of create_webhook.

Webhooks id, 1 operation

delete_webhookDelete webhookDELETEAgents: ask firstDeletes a webhook permanently.

Showing the first 120 of 126 endpoints. The rest are in the product, searchable from the workflow builder and from chat.

Use Ploomes from Claude Code, Cursor or Codex

Connect Ploomes in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ploomes 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 Ploomes

Create your workspace
Sign up free. Nothing to install.
Connect Ploomes once
Add your Ploomes 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.