Repository navigation
Connectors block 7: weclapp writes, Mercado Libre listings, Wildberries reviews, Telegram albums, Google Maps, ServiceNow, Tavily, Perplexity, SerpApi - #1069
Merged
Conversation
The weclapp adapter only read. Five Cloud workspaces were building write tools by hand; the busiest sets the responsible user on invoices, orders and customers with a partial PUT (1,353 of 1,361 calls succeed). Adds 31 tools: create and partially edit parties (customers, suppliers, contact persons, leads), quotations and sales orders with positions, sales order and quotation status, cancel an order, invoice an order, edit invoices, tasks, comments, time records, articles and their prices, stock bookings in and out, purchase orders, and a reference-data lookup for the ids writes need. Edits use weclapp's documented ignoreMissingProperties=true so fields left out keep their values, with optional version locking and dryRun. Deletes ship switched off. No name reuses one that workspaces gave their own weclapp tools. Catalog updates now create a tool the catalog ships switched off as switched off, as a fresh install does; before, applying an update turned such tools on. Adds weclapp error hints for read-only fields and optimistic lock errors.
…ram albums Mercado Libre (14 new tools): category predictor, category, attributes, sale terms and listing types; the seller's listings; validate, create and update a listing; pause or reactivate; close (installed switched off); read, add and replace the description. Create and validate take family_name for User Products sellers, the body that works in workspaces' own create tools. Instructions rewritten around the listing flow. Wildberries (12 new tools): unanswered counts, new feedbacks and questions, list and read feedbacks, answer and edit an answer, list and answer questions, reject a question (switched off), list return claims and decide on one. Each tool calls feedbacks-api or returns-api directly with the same token. Instructions now spell out the Base token limit of 5 calls an hour that made a hand-built answer tool fail with 429 on half its calls. Telegram Bot (5 new tools): send_album (sendMediaGroup), animation, sticker, contact and venue. Named send_album because three workspaces already have their own telegram_bot_send_media_group. Catalog re-sync: a tool the catalog ships switched off is now created switched off when an existing connector takes the update, as at install.
Google Maps (9 tools, read-only) calls Places API (New), Geocoding API v4 and Routes API with an X-Goog-Api-Key: text and nearby search, place details, photo links, autocomplete with session tokens, geocoding both ways, routes and route matrices. Default field masks stay on the Pro tier and the instructions map fields to SKUs and prices; the install check is the free ID-only Place Details call. Google's Maps Grounding Lite MCP server was considered and not bridged: it has no details, reviews, photos, autocomplete, geocoding or matrices. ServiceNow (36 tools) uses the Table, Aggregate, Service Catalog, CMDB Instance and Attachment APIs with Basic auth on https://<instance>.service-now.com, with OAuth documented as a switch in the connector settings. Incidents (resolve sets state 6 and close sets 7, both with close_code and close_notes), change requests, problems, requests and RITMs with their variables, catalog search and ordering, knowledge search, users, groups, CMDB items with relationships, a generic table query, counts, choice lists and attachments. Writes ask for confirmation; record deletion installs switched off. The official MCP Server Console needs Now Assist and admin-defined tools, so REST it is. Both listed; quoted counts 380 -> 382; logos from simple-icons (Google Maps) and the ServiceNow mark in the brand green.
Three REST connectors for web search used by AI agents, all listed.
Counts: 383 adapters, 19 keyless.
Tavily (7 tools): search, extract, map, crawl, background research
start and poll, usage. Bearer key. Defaults stay cheap (basic depth,
5 results, crawl and map limits with a 25 s Tavily timeout so calls end
inside the 30 s engine timeout). Body fields, enums and bounds checked
against Tavily's OpenAPI document; Tavily validates bodies before the
key, so a 401 with a wrong key on every tool confirms the bodies pass.
Perplexity API (7 tools): Agent API answers with the fast or low preset
and web_search filters, the Search API, Sonar chat completions (sonar,
sonar-pro, sonar-reasoning-pro), background research runs on medium,
high or xhigh with get and cancel, and the model list. Perplexity ended
support for Sonar Chat Completions on 27 Sep 2026 and no longer serves
async Sonar, so deep research runs as an Agent API background run and
the Sonar tool points to perplexity_ask. Checked against the OpenAPI
document; every route answers a wrong key with 401.
SerpApi (11 tools): Google web search, News, Images, Maps, Shopping,
Scholar and Trends, YouTube, Bing, account and locations. The key goes
in the encrypted authConfig and QUERY_AUTH adds it as api_key, so no
tool carries it; the secret guard accepts the {{VAR}} reference.
Parameters checked against SerpApi's per-engine catalog; every search
tool was run on SerpApi's keyless demo query and its answer trimmed to
the useful blocks with empty fields dropped.
Runtime error hints for the three hosts (401, 402/432/433 credits,
429, 400/422). Logos: Perplexity from simple-icons, Tavily and SerpApi
from the vendors' own sites.
…into helpcode/connectors-block7
… helpcode/connectors-block7 # Conflicts: # packages/backend/src/connectors/catalog-resync.service.spec.ts # packages/backend/src/connectors/catalog-resync.service.ts
…w' into helpcode/connectors-block7
…helpcode/connectors-block7 # Conflicts: # CITATION.cff # README.de.md # README.ja.md # README.md # README.zh-CN.md # glama.json # package.json # server.json
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…ring check in the Tavily spec
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This block is driven by the 12 Oct demand review: catalog searches, connectors that workspaces built by hand, and the remaining gaps in the catalog comparison. The adapter count goes from 380 to 385, and the tool count to 5,430.
Extensions of listed adapters. They reach existing installs through the normal catalog update. None of the new tool names matches a tool a customer created on those connectors; this was checked against prod.
ignoreMissingProperties=true. They take an optionalversionfor optimistic locking and adryRunflag.titleorfamily_nameis accepted, because sellers on the User Products model needfamily_name.New connectors
Fix in
catalog-resync.service.ts. Applying a catalog update used to create new tools switched on, even when the catalog ships them switched off. They now arrive switched off, as on a fresh install.