lemlist (BYOK)
Read your lemlist campaigns, campaign statistics, lead states, schedules, templates and credits with your own API key
Read your Zuper service setup: service territories, teams, request statuses and workflow automation rules with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_service_territoriesget_service_territorylist_teamslist_request_statuseslist_workflowslist_workflow_modulesZuper Setup (BYOK) lets an AI assistant read your own Zuper Setup data through the Zuper Setup API with a key you supply (Zuper API key). Read-only: 6 tools (list_service_territories, get_service_territory, list_teams, list_request_statuses, list_workflows, list_workflow_modules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.zuperpro.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zuper Setup. Zuper Setup and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Zuper Setup API (*.zuperpro.com) with a BYOK key; documentation: https://developers.zuper.co/reference/get-service-territories. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-zuper-service-config.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-zuper-service-config.connectorbay.com/mcpPOST https://byok-zuper-service-config.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-zuper-service-config.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developers.zuper.co).Zuper Setup (BYOK) lets an AI assistant read your own Zuper Setup data through the Zuper Setup API with a key you supply (Zuper API key). It is a hosted MCP server with 6 tools such as List service territories, Get service territory, List teams, List request statuses, List workflows, List workflow modules, published by Unify Dynamics LLC. It is independent and not affiliated with Zuper Setup.
Add the MCP endpoint https://byok-zuper-service-config.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-zuper-service-config.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-zuper-service-config.json.
Yes: this is a bring-your-own-key connector. Create a Zuper API key at https://developers.zuper.co/docs/getting-started and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your lemlist campaigns, campaign statistics, lead states, schedules, templates and credits with your own API key
Read your Lever recruiting data (opportunities, job postings, requisitions, stages, users) with BYOK
Read your Lightspeed Retail (X-Series) price books, promotions, tags and variant attributes with your own personal token
Read your Lightspeed Retail (X-Series) account settings, online sales channels, register button layouts and custom field definitions with your own personal token
Read your Limble CMMS maintenance data: assets, work orders and tasks, parts, vendors, purchase orders, locations and statuses, with your own API client ID and secret
Read your Limitless Pendant lifelogs (recorded conversations and notes) and Ask AI chats with your own API key
https://byok-zuper-service-config.connectorbay.com/mcpPOST https://byok-zuper-service-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-zuper-service-config.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-zuper-service-config.connectorbay.com/health · Tool schemas: https://byok-zuper-service-config.connectorbay.com/tools.jsonZuper Setup (BYOK) lets an AI assistant read your own Zuper Setup data through the Zuper Setup API with a key you supply (Zuper API key). Read-only: 6 tools (list_service_territories, get_service_territory, list_teams, list_request_statuses, list_workflows, list_workflow_modules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.zuperpro.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zuper Setup. Zuper Setup and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
list_service_territories: List service territories with name, description, type (zip code, radius or map area), colour, active flag and dates.get_service_territory: Get one service territory by uid with name, description, type, colour, active flag and dates.list_teams: List teams with name, colour, description, time zone, number of users and active flag (no member details).list_request_statuses: List the configured customer request statuses with uid, name, type and colour.list_workflows: List workflow automation rules with name, trigger module and event, access scope and active flag.list_workflow_modules: List the modules that can trigger workflows (jobs, requests, and so on) with their display names.You bring your own Zuper Setup Zuper API key (https://developers.zuper.co/docs/getting-started). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.zuperpro.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Live from the Zuper Setup API (*.zuperpro.com) with a BYOK key; documentation: https://developers.zuper.co/reference/get-service-territories. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zuper Setup. Zuper Setup and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Zuper Setup account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Zuper Setup (BYOK) is. Zuper Setup (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Zuper Setup data: Read your Zuper service setup: service territories, teams, request statuses and workflow automation rules with your own API key. You bring your own Zuper Setup Zuper API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Zuper Setup call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to *.zuperpro.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Zuper Setup rejects it, we say so without repeating it.
What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Zuper Setup receives. The request we make on your behalf, including the key and the arguments, under Zuper Setup's own terms and privacy policy. Zuper Setup acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Zuper Setup gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.
What we do not do. We do not build a profile, sell or share personal information, or keep your Zuper Setup data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.
Sub-processors. Zuper Setup (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).
Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Zuper Setup at any time to end all access.
Children. Zuper Setup (BYOK) is a general-audience service operated by the adult using the assistant, under Zuper Setup's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Zuper Setup (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-zuper-service-config.connectorbay.com/mcphttps://byok-zuper-service-config.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Zuper Setup (BYOK) never asks for them.